http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60732
--- Comment #4 from Brooks Moses <brooks at gcc dot gnu.org> --- Interesting. As noted, with -fabi-version=[1 to 3] on Linux, I was getting both sets. Mike, what do you think is the best solution here? We could use Dominique's patch with a comment to the effect that "New-ABI symbols are always emitted on Linux, but only with -fabi-version=4 or later on Darwin." We could revert my change and hardcode -fabi-version=2 for all targets. Or we could take the suggestion from your original review email and duplicate the test into new-ABI and old-ABI versions, and do both of those. (If we duplicate the test, is altivec-7a.C a reasonable name for the duplicate-with-different-ABI, or does it need to be altivec-18.C or whatever the next available number is?)
