diff options
| author | Craig Topper <craig.topper@intel.com> | 2020-06-26 16:41:30 -0700 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2020-06-26 16:45:44 -0700 |
| commit | d298acde828f4abc5e7c82ba1f6092890d910097 (patch) | |
| tree | 3400658fc2655595c3a0f6d2c36b720480bb728d /clang/lib/CodeGen/CodeGenFunction.cpp | |
| parent | c918c1a91a03f612c1b1e81b82460fbf80fc592a (diff) | |
| download | llvm-d298acde828f4abc5e7c82ba1f6092890d910097.zip llvm-d298acde828f4abc5e7c82ba1f6092890d910097.tar.gz llvm-d298acde828f4abc5e7c82ba1f6092890d910097.tar.bz2 | |
[X86] Don't disable xsave when avx is disabled. Implicitly enable xsave with avx is enabled and xsave wasn't explciitly disabled
CPUs with avx always have xsave, but some CPUs without avx also
have xsave. So we shouldn't disable xsave just because avx is
disabled. This would prevent xsave from being enabled with
-march=native on CPUs with xsave and not avx.
But we also don't want -mavx -mno-avx to leave xsave eanabled.
So only enable xsave if avx is enabled after processing all features.
I thought about just not turning xsave on with avx at all, but
there might be someone out there depending on it.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenFunction.cpp')
0 files changed, 0 insertions, 0 deletions