Re: march=native fails with newer hardware

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

 



On Fri, 9 Apr 2021 at 19:57, Jonathan Brandmeyer wrote:
>
> 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 have you got a gcc driver that disagrees with cc1 about what is
supported? They're supposed to come from the same release.

> 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.

Can't you just use -march=icelake instead of -march=native?



[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