This is needed to make the v64i8 and v32i16 types legal for the 512-bit VBMI instructions. Fixes PR30912.
Details
- Reviewers
zvi delena - Commits
- rG6c7ecc534139: [AVX-512] Make VBMI instruction set enabling imply that the BWI instruction set…
rC286340: [AVX-512] Make VBMI instruction set enabling imply that the BWI instruction set…
rL286340: [AVX-512] Make VBMI instruction set enabling imply that the BWI instruction set…
Diff Detail
Event Timeline
lib/Basic/Targets.cpp | ||
---|---|---|
3353 | is -> if | |
test/Preprocessor/x86_target_features.c | ||
212 | Test is turning on and then off the same feature. Did you mean -mavx512bw -mno-avx512vbmi ? If the latter, I would prefer the compiler shout at me for providing contradicting flags than let the last flag win. Consider enforcing this in handleTargetFeatures(). |
test/Preprocessor/x86_target_features.c | ||
---|---|---|
212 | It was supposed to be -mavx512vbmi -mno-avx512bw to verify that turning off bwi would turn off vbmi. The lack of warning is consistent with the behavior of all the other linked feature flags. |
is -> if