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:58:19 +0100 [thread overview]
Message-ID: <CAH6eHdRkXMw5qa6mUKsaDcop=MzSe8HS4WPnV89M5PBiU=Rhqw@mail.gmail.com> (raw)
In-Reply-To: <B66D0A9BD99A4783B95EDD0B963F6DCE@H270>
On Fri, 26 May 2023 at 15:34, Stefan Kanthak <stefan.kanthak@nexgo.de> wrote:
>
> "Jonathan Wakely" <jwakely.gcc@gmail.com> wrote:
>
> > On Fri, 26 May 2023 at 14:55, Stefan Kanthak <stefan.kanthak@nexgo.de> wrote:
>
> [...]
>
> >> NOT obvious is but that -m<feature> -march=<lowerISA> does not clear any
> >> <feature> not supported in <lowerISA>, i.e the last one does NOT win here.
> >
> > The last -march option selects the base set of instructions. The -mISA
> > options modify that base.
>
> You but missed the point, AGAIN: the modifications per -mISA and -mno-ISA
> persist, i.e. they are NOT reset by the last -march= option.
Nobody said they are reset, and the docs don't say that, so assume they are not.
The last -march option selects a base and the -mISA options modify the
base. Note *the* base. The one that was selected. By the last -march
option. The base.
> Is this SOOOO hard to grok?
I understand your question. It's based on failing to read or
understand what has been said.
There is a base ISA. Then there are additions or subtractions relative
to that base. That's it. That actually tells you everything you need
to know, if you just apply some thought.
Choosing a base does not remove the effects of the additions or
subtractions, because they are additions and subtractions relative to
whichever base arch is in effect.
Where the -misa options appear on the command line relative to -march
doesn't matter, which is why it doesn't need to be stated explicitly.
The order only matters for -march relative to other -march options,
and -misa options relative to other -misa options.
> Is this soooo hard to document?
I prefer arguing with trolls, it's even easier.
next prev parent reply other threads:[~2023-05-26 14:58 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
2023-05-26 15:07 ` Stefan Kanthak
2023-05-26 14:26 ` Stefan Kanthak
2023-05-26 14:58 ` Jonathan Wakely [this message]
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='CAH6eHdRkXMw5qa6mUKsaDcop=MzSe8HS4WPnV89M5PBiU=Rhqw@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).