public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100347] [11/12 Regression] GCC 11 does not recognize skylake; translates "march=native" to "x86_64"
Date: Thu, 06 May 2021 08:09:49 +0000 [thread overview]
Message-ID: <bug-100347-4-DnxqA4FdBR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100347-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100347
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
> (In reply to Iru Cai from comment #6)
> > I've checked host_detect_local_cpu() in gcc/config/i386/driver-i386.c. GCC
> > detects x86 host CPU micro architecture by cpuid instruction instead of the
> > APIs provided by the OS.
>
> But there shouldn't have been any functional changes in the code 10.x vs.
> 11.x
>
> Erik - does GCC 10.3 actually still work? Thus, isn't it maybe some OS
> restriction on CPUID access, maybe a difference in whether the GCC binaries
> are signed or not?
>
> I wonder if you can try
>
> int main()
> {
> __builtin_cpu_init ();
> return __builtin_cpu_is ("skylake");
> }
>
> with both compilers?
I recently went through the exercise of finding out what -march=native reported
for me across the machines I use for testing - AFAIR the Xeon W reported
cascadelake, and corei7s reported skyline, ivybridge or haswell. I will need
to recheck.
Are you on Darwin20 / macOS11 .. it seems that Apple are gradually trying to
tie things down more in line with iOS - however, I have not seen too much of
that on x86_64 - more on the Arm64 side.
I'll need a few days to check this out.
next prev parent reply other threads:[~2021-05-06 8:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 23:34 [Bug driver/100347] New: " schnetter at gmail dot com
2021-04-29 23:35 ` [Bug driver/100347] " schnetter at gmail dot com
2021-04-30 6:59 ` [Bug target/100347] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-04-30 8:38 ` jakub at gcc dot gnu.org
2021-04-30 8:39 ` jakub at gcc dot gnu.org
2021-04-30 13:24 ` schnetter at gmail dot com
2021-05-06 7:46 ` mytbk920423 at gmail dot com
2021-05-06 8:00 ` rguenth at gcc dot gnu.org
2021-05-06 8:09 ` iains at gcc dot gnu.org [this message]
2021-05-06 8:30 ` jakub at gcc dot gnu.org
2021-05-06 11:20 ` iains at gcc dot gnu.org
2021-05-06 12:29 ` iains at gcc dot gnu.org
2021-05-06 12:32 ` schnetter at gmail dot com
2021-05-06 12:54 ` schnetter at gmail dot com
2021-05-06 13:34 ` iains at gcc dot gnu.org
2021-05-07 12:27 ` schnetter at gmail dot com
2021-05-07 13:28 ` iains at gcc dot gnu.org
2021-05-09 9:26 ` iains at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2022-01-05 14:43 ` rguenth at gcc dot gnu.org
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2022-07-26 13:38 ` [Bug target/100347] [11/12/13 " 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-100347-4-DnxqA4FdBR@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).