These were missed in SVN r316783, which broke compiling mingw-w64 CRT.
isValidFeatureName should use the same spellings as used in initFeatureMap, not the ones used in hasFeature.
Differential D39631
[X86] Fix the spelling of 3dnow and 3dnowa in isValidFeatureName mstorsjo on Nov 4 2017, 1:06 PM. Authored by
Details These were missed in SVN r316783, which broke compiling mingw-w64 CRT. isValidFeatureName should use the same spellings as used in initFeatureMap, not the ones used in hasFeature.
Diff Detail Event TimelineComment Actions Can we just add -Werror to test/CodeGen/3dnow-builtins.c to test this? I believe it should be throwing a warning currently. Can we also remove mm3dnow and mm3dnowa from the isValidFeatureName? Comment Actions That file actually already has got -Werror
It doesn't. That test enables the feature via -target-feature +3dnowa on the command line, which is accepted even if it isn't matched in isValidFeatureName, and the header declaration doesn't trigger any warnings.
The clang tests seem to pass with that removed at least (and nothing in mingw-w64 seems to refer to it in that form so it should probably be fine) - I can update the patch (and retest building mingw-w64) with that change if you want it squashed. Comment Actions Ok then we can keep the new test. I believe the isValidFeature list was copied from the list in hasFeature. But isValidFeature should match the names used by initFeatureMap since that's what we use to look them up. |