public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cdotts at planetiq dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100009] New: -march=native doesn't recognize tigerlake
Date: Fri, 09 Apr 2021 22:40:33 +0000	[thread overview]
Message-ID: <bug-100009-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100009

            Bug ID: 100009
           Summary: -march=native doesn't recognize tigerlake
           Product: gcc
           Version: 9.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: cdotts at planetiq dot com
  Target Milestone: ---

Copied from email chain: 
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.

Response from Jim Wilson: 
Looks like a bug in gcc-9.  tigerlake was added to
gcc/config/i386/driver-i386.c but not to the arch_names_table in i386.c.  I
would suggest filing a bug report.  I don't think there is a way to workaround
this.  It needs to be fixed in the gcc source tree.

             reply	other threads:[~2021-04-09 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 22:40 cdotts at planetiq dot com [this message]
2021-04-10 10:46 ` [Bug target/100009] [9 Regression] " redi at gcc dot gnu.org
2021-04-12  8:11 ` [Bug target/100009] [9 Regression] -march=native doesn't work on tigerlake rguenth at gcc dot gnu.org
2021-04-12  9:50 ` crazylht at gmail dot com
2021-04-13  2:04 ` crazylht at gmail dot com
2021-04-15  9:38 ` crazylht at gmail dot com
2021-04-30 11:12 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100009-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).