From: "Paul A. Clarke" <pc@us.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
wschmidt@linux.ibm.com, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Better error messages for power8/9-vector builtins
Date: Wed, 17 Nov 2021 14:25:11 -0600 [thread overview]
Message-ID: <20211117202511.GD7755@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com> (raw)
In-Reply-To: <20211117200002.GT614@gate.crashing.org>
On Wed, Nov 17, 2021 at 02:00:02PM -0600, Segher Boessenkool wrote:
> On Wed, Nov 17, 2021 at 11:45:02AM -0600, Paul A. Clarke wrote:
> > I guess I'm being pedantic. "requires -mcpu=power8 and -mvsx" is not
> > accurate from a user's point a view, as "-mcpu=power8" is sufficient,
> > since "-mvsx" is enabled when "-mcpu=power8" is specified.
>
> To be really pedantic, -mcpu=power8 isn't required either: anythng that
> enable the subset of ISA 2.07 that is needed is enough already. But we
> don't want to encourage users to use those interfaces.
>
> > The real "requires" is "-mcpu=power8" and no "-mno-vsx".
>
> And no -mno-altivec. And and and. There is a huge web.
>
> > It's not a strong objection, since specifying "-mno-vsx" should be
> > uncommon. (Right?) And, specifying "-mcpu=power8 -mvsx" is harmless.
>
> Maybe the warning could say "requires -mcpu=power8 (and -mvsx)"? Is
> that clearer, to your eye?
Hrm. No, but let me withdraw my expression of concern. Both "power8" and
"vsx" are required, and those two options get that explicitly.
That "-mcpu=power8" also pulls in "-mvsx" is a subtlety that is
perhaps not terribly relevant.
Thanks for entertaining my concern, but we've spent too much time on it
already. :-)
PC
next prev parent reply other threads:[~2021-11-17 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 17:12 Bill Schmidt
2021-11-17 16:54 ` Paul A. Clarke
2021-11-17 17:00 ` Bill Schmidt
2021-11-17 17:45 ` Paul A. Clarke
2021-11-17 20:00 ` Segher Boessenkool
2021-11-17 20:04 ` David Edelsohn
2021-11-17 20:25 ` Paul A. Clarke [this message]
2021-11-17 20:29 ` Segher Boessenkool
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=20211117202511.GD7755@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com \
--to=pc@us.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.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).