From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bill Schmidt <wschmidt@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Builtins test changes for BFP scalar tests
Date: Thu, 18 Nov 2021 15:18:39 -0600 [thread overview]
Message-ID: <20211118211839.GA614@gate.crashing.org> (raw)
In-Reply-To: <37a1c5e8-a9ca-f5d9-74f3-0a7d82e30a7d@linux.ibm.com>
On Thu, Nov 18, 2021 at 07:32:27AM -0600, Bill Schmidt wrote:
> >>> error: '__builtin_vsx_scalar_extract_sig' requires the '-mcpu=power9' option and either the '-m64' or '-mpowerpc64' option
> >>> note: builtin '__builtin_vec_scalar_extract_sig' requires builtin '__builtin_vsx_scalar_extract_sig'
> >> The rhs in the note does not *exist*, as far as the user is concerned.
> >> One builtin requiring another is all gobbledygook.
> > As stated above, this isn't something new that I've added. That's what
> > we already do. It's how the overload error messages have always been.
>
> That said, I don't like the "requires" language at all, either. How about
> replacing "builtin X requires builtin Y" with "overloaded builtin X is
> implemented by builtin Y" as a better explanation?
That is better (although builtin Y *does not exist* as far as the user
is concerned: it is not documented, and you cannot write it in source
code afaics).
Segher
next prev parent reply other threads:[~2021-11-18 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 20:58 Bill Schmidt
2021-11-17 21:32 ` Segher Boessenkool
2021-11-17 23:06 ` Bill Schmidt
2021-11-18 13:32 ` Bill Schmidt
2021-11-18 21:18 ` Segher Boessenkool [this message]
2021-11-18 21:16 ` Segher Boessenkool
2021-11-18 21:30 ` Bill Schmidt
2021-11-18 21:32 ` Segher Boessenkool
2021-11-18 21:59 ` Bill Schmidt
2021-12-01 21:16 ` Segher Boessenkool
2021-12-01 16:31 ` [PATCH, PING] " Bill Schmidt
2021-12-01 21:29 ` [PATCH] " 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=20211118211839.GA614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.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).