r233672
http://reviews.llvm.org/D8694
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
___
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
The target-cpu is still used for LLVM features that don't have a real CPUID
bit. For instance, slow-bt-mem and slow-incdec. It would also still be used to
pick the scheduling model.
http://reviews.llvm.org/D8694
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
This is fine by me, but I am not sure if I should be the one to LGTM it.
Does this make passing -target-cpu for native redundant?
http://reviews.llvm.org/D8694
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
___
Looks good, go for it.
http://reviews.llvm.org/D8694
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
___
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
I think this should be ok. It'll turn some hidden features that would
have been target-cpu features into target-features features explicitly,
but that'll just mean wordier attribute descriptions (and will be more
accurate).
-eric
On Sun, Mar 29, 2015 at 9:16 PM Craig Topper
Hi chandlerc, echristo, rafael, grosbach,
Some versions of Sandybridge, Ivybridge, Haswell, and Broadwell CPUs don't
support AVX. Currently, getHostCPUName changes the CPU name to Nehalem when it
detects one of the CPUs. This also ends up disabling other features that these
CPUs might still
