aboutsummaryrefslogtreecommitdiff
path: root/gcc/explow.c
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-09-08 12:23:49 +0000
committerGitHub <noreply@github.com>2021-09-08 12:23:49 +0000
commit52fb10b1e0ffe4f026ad9728c757c5e41ebac865 (patch)
tree70e1e0d3107c9307da1cda36f69f9b6a68ad2c02 /gcc/explow.c
parent8a9271e1921d0eac46bda889da6508cf94d32682 (diff)
parent37f3b02bf8edbf707e6156feec593b9b0d7da027 (diff)
downloadgcc-52fb10b1e0ffe4f026ad9728c757c5e41ebac865.zip
gcc-52fb10b1e0ffe4f026ad9728c757c5e41ebac865.tar.gz
gcc-52fb10b1e0ffe4f026ad9728c757c5e41ebac865.tar.bz2
Merge #656
656: Add mangling switch r=philberty a=CohenArthur Add option to choose mangling scheme. Closes #429 This PR splits the `Mangler` class in its own set of header and source and adds the base for v0 name mangling. You are now able to specify the mangling scheme to use using `-frust-mangling=<value>`. When inputting an invalid value, the compiler errors out using `unrecognized command-line option `-frust-mangling=<not_valid>`. Is there a better way to do this? Is there also a way to test this behaviour using dejagnu? Co-authored-by: CohenArthur <arthur.cohen@epita.fr>
Diffstat (limited to 'gcc/explow.c')
0 files changed, 0 insertions, 0 deletions