From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Stefan Kanthak <stefan.kanthak@nexgo.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc@gnu.org, Andrew Pinski <pinskia@gmail.com>
Subject: Re: Will GCC eventually support SSE2 or SSE4.1?
Date: Fri, 26 May 2023 15:55:11 +0100 [thread overview]
Message-ID: <CAH6eHdRPzvn_1+SVCiNm_wEaEESzCk3Rak_h-F+hhsKjQUZjKg@mail.gmail.com> (raw)
In-Reply-To: <D79383C0D8334C829C921C20EDD120E4@H270>
On Fri, 26 May 2023 at 15:48, Stefan Kanthak <stefan.kanthak@nexgo.de> wrote:
>
> "Jakub Jelinek" <jakub@redhat.com> wrote:
>
> [...]
>
> > And for -m32 it is also the last option that wins, but as with
> > many other cases just last one from certain set of options. [...]
> > The -mISA options are processed left to right after
>
> as well as BEFORE
No. You seem to be interpreting "after" to mean "later in the command
line" but Jakub means *at a later time*. He used "left to right" to
describe position in the command line, and "after" means "at a later
time".
Any -march options are processed first, from left to right. After
that, there is a base arch in effect.
Then, after that, the -mISA options are processed, and take effect
relative to the base arch.
What Jakub wrote is correct. If you try a bit harder to understand
what has been said repeatedly, you might get it.
>
> > setting base from -march=.
>
> In other words: although -march= selects a (documented sub)set of
> -mISA options, it does NEITHER reset any -mISA option set NOR any
> -mno-ISA option reset BEFORE or AFTER itself, i.e. all -m[no-]ISA
> options have precedence even if they preceed -march=.
>
> Just document that!
That is not far from unreadable.
next prev parent reply other threads:[~2023-05-26 14:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:46 Stefan Kanthak
2023-05-26 7:00 ` Andrew Pinski
2023-05-26 7:30 ` Jonathan Wakely
2023-05-26 7:58 ` Stefan Kanthak
2023-05-26 8:16 ` Sam James
2023-05-26 8:28 ` Jonathan Wakely
2023-05-26 8:59 ` Stefan Kanthak
2023-05-26 9:22 ` Jakub Jelinek
2023-05-26 11:28 ` Stefan Kanthak
2023-05-26 11:42 ` Jonathan Wakely
2023-05-26 12:03 ` Stefan Kanthak
2023-05-26 12:16 ` Jonathan Wakely
2023-05-26 12:22 ` Stefan Kanthak
2023-05-26 13:00 ` Mark Wielaard
2023-05-26 12:23 ` Jonathan Wakely
2023-05-26 11:36 ` Stefan Kanthak
2023-05-26 11:45 ` Jonathan Wakely
2023-05-26 12:19 ` Stefan Kanthak
2023-05-26 12:30 ` Jonathan Wakely
2023-05-26 12:42 ` Stefan Kanthak
2023-05-26 13:33 ` Nicholas Vinson
2023-05-26 12:37 ` Jakub Jelinek
2023-05-26 13:49 ` Stefan Kanthak
2023-05-26 14:07 ` Jonathan Wakely
2023-05-26 14:18 ` Jakub Jelinek
2023-05-26 14:41 ` Stefan Kanthak
2023-05-26 14:55 ` Jonathan Wakely [this message]
2023-05-26 15:07 ` Stefan Kanthak
2023-05-26 14:26 ` Stefan Kanthak
2023-05-26 14:58 ` Jonathan Wakely
2023-05-26 15:49 ` Stefan Kanthak
2023-05-26 16:44 ` David Brown
2023-05-27 18:16 ` Will GCC eventually support correct code compilation? Dave Blanchard
2023-05-27 18:59 ` Jason Merrill
2023-05-28 11:50 ` David Brown
2023-05-26 9:22 ` Will GCC eventually support SSE2 or SSE4.1? Jonathan Wakely
2023-05-26 8:12 ` Hagen Paul Pfeifer
2023-05-26 9:51 ` Jonathan Wakely
2023-05-26 11:34 ` Nicholas Vinson
2023-05-26 15:10 ` LIU Hao
2023-05-26 15:40 ` Stefan Kanthak
2023-05-27 18:20 ` LIU Hao
2023-05-27 18:49 ` Stefan Kanthak
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=CAH6eHdRPzvn_1+SVCiNm_wEaEESzCk3Rak_h-F+hhsKjQUZjKg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gnu.org \
--cc=jakub@redhat.com \
--cc=pinskia@gmail.com \
--cc=stefan.kanthak@nexgo.de \
/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).