btver1 is a SSSE3/SSE4a only CPU - it doesn't have AVX and doesn't support XSAVE.
This looks like some kind of copy+paste error from bdver1.
LLVM companion to D17682.
Differential D17683
[X86] AMD Bobcat CPU (btver1) doesn't support XSAVE
RKSimon on Feb 27 2016, 12:36 PM. Authored by
Details btver1 is a SSSE3/SSE4a only CPU - it doesn't have AVX and doesn't support XSAVE. This looks like some kind of copy+paste error from bdver1. LLVM companion to D17682.
Diff Detail
Event TimelineComment Actions LGTM. I seem to be the one that added it in the first place, but I was just bulk adding to many processors and I guess got carried away. Comment Actions I've gone through the 14h BKDG and can't find any reference to XSAVE/XSAVEOPT at all. I'll try to dig up a bobcat laptop from somewhere to confirm but I think this is correct. The only reason I noticed this is that clang (correctly I believe) auto-enables AVX for XSAVE capable targets meaning we generate VEX-encoded instructions for btver1! http://support.amd.com/TechDocs/43170_14h_Mod_00h-0Fh_BKDG.pdf Comment Actions Apparently I'm the one who made clang do that and I don't know why. gcc doesn't do that as far as I can tell. I'm going to remove that. Comment Actions Craig - thanks for the XSAVE/AVX fix. I've got a /proc/cpuinfo dump now for a typical bobcat cpu (first core below) - XSAVE is not present. Am I OK to commit this and D17682 ? processor : 0 Comment Actions Craig - just wanted to double check you're happy with both these patches before committing? Cheers, Simon. |