march=native fails with newer hardware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



We're using GCC v9.3.0 on a newer laptop, as packaged by Ubuntu for
20.04 LTS.  Our build for host-native tools naturally enables
cpu-specific optimization with `-march=native`.  The gcc driver is
passing -march=tigerlake down to cc1 (or cc1plus).  The driver
program's auto-detection is correct in that this is tiger lake
hardware.  However, it is not supported in this release of GCC.

How exactly is the driver coming up with this code name?  I'd like to
keep the Makefile set up as-is for the whole team.  Can we override
the definition of `native` through an environment variable or
something?  Ice lake client optimizations and instruction selection
appear to be working for our usage.  We can modify the Makefile to be
sensitive to an environment variable, but I'm wondering if GCC itself
can also be overridden in this way.

Thanks,
-- 
Jonathan Brandmeyer



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux