From: NightStrike <nightstrike@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: unlvsur unlvsur <unlvsur@live.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: how to get -march=native's value?
Date: Thu, 16 Sep 2021 22:46:44 -0400 [thread overview]
Message-ID: <CAF1jjLvPXz-Wfc5F2e0-5VhefpPPD1oY1H+2YvTy6sc5e8oxkg@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQ+Ve_E5SW6w=XxdvszphyPS1x-2WuM9mHPZEn7PpDV7Q@mail.gmail.com>
On Tue, Sep 7, 2021 at 3:57 AM Jonathan Wakely via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> On Tue, 7 Sep 2021, 08:03 unlvsur unlvsur via Gcc-help, <
> gcc-help@gcc.gnu.org> wrote:
>
> > I try to cross compile to another slower machine. -march=native works on
> > that architectures, but I would like to know what is the value of
> > -march=??? For -march=native. Is there a way to print march value out??
> >
>
> It doesn't choose a single value. It enables all the individual options
> like -msse and that combination of options might not correspond to any
> particular -march value.
Is that true? I mean, in principle, I know I've reported a bug where
-march=native scanned /proc/cpuinfo (or however it got the info) and
came up with a different result than -march=k8 (or whatever I was
reporting at the time), but that was a bug that some helpful people
fixed. If gcc doesn't have an -march for a particular esoteric arch,
then fine, but if it does, I'd think that this would be a bug similar
to what I experienced previously.
next prev parent reply other threads:[~2021-09-17 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 7:02 unlvsur unlvsur
2021-09-07 7:56 ` Jonathan Wakely
2021-09-17 2:46 ` NightStrike [this message]
2021-09-17 8:29 ` Xi Ruoyao
2021-09-17 10:26 ` Jonathan Wakely
2021-09-17 10:38 ` Jonathan Wakely
2021-09-17 17:53 ` Segher Boessenkool
2021-09-27 12:55 ` Vincent Lefevre
2021-09-27 17:13 ` Segher Boessenkool
2021-09-27 18:14 ` L A Walsh
2021-09-27 18:25 ` Jonathan Wakely
2021-09-27 20:26 ` Segher Boessenkool
2021-09-27 20:30 ` NightStrike
2021-09-27 18:26 ` Florian Weimer
2021-09-07 7:59 ` Hongtao Liu
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=CAF1jjLvPXz-Wfc5F2e0-5VhefpPPD1oY1H+2YvTy6sc5e8oxkg@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=unlvsur@live.com \
/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).