On Mon, Feb 17, 2014 at 8:34 PM, Jakub Jelinek <ja...@redhat.com> wrote:
> As discussed in the PR, because -mf16c implies -mavx, if the CPU has > F16C (and AVX) support, but OS doesn't save YMM state, we shouldn't > be passing -mf16c. > > Also, as noticed by Uros, the clearing of has_fma4 and has_xop if > OS doesn't save YMM state was done before it was set. > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > 2014-02-17 Jakub Jelinek <ja...@redhat.com> > Uros Bizjak <ubiz...@gmail.com> > > PR driver/60233 > * config/i386/driver-i386.c (host_detect_local_cpu): If > YMM state is not saved by the OS, also clear has_f16c. Move > CPUID 0x80000001 handling before YMM state saving checking. OK for mainline and release branches. Thanks, Uros.
