From: Segher Boessenkool <segher@kernel.crashing.org>
To: Martin Liska <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] rs6000: Adjust error messages.
Date: Wed, 23 Mar 2022 06:17:34 -0500 [thread overview]
Message-ID: <20220323111734.GA614@gate.crashing.org> (raw)
In-Reply-To: <202203231033.22NAXRWD013233@gate.crashing.org>
On Wed, Mar 23, 2022 at 11:31:12AM +0100, Martin Liska wrote:
> --- a/gcc/config/rs6000/rs6000.cc
> +++ b/gcc/config/rs6000/rs6000.cc
> @@ -4345,8 +4345,8 @@ rs6000_option_override_internal (bool global_init_p)
> rs6000_veclib_handler = rs6000_builtin_vectorized_libmass;
> else
> {
> - error ("unknown vectorization library ABI type %qs for "
> - "%qs switch", rs6000_veclibabi_name, "-mveclibabi=");
> + error ("unknown vectorization library type in "
> + "%<-mveclibabi=%s%>", rs6000_veclibabi_name);
"ABI type".
Okay for trunk with that restored. Thanks!
Segher
next parent reply other threads:[~2022-03-23 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202203231033.22NAXRWD013233@gate.crashing.org>
2022-03-23 11:17 ` Segher Boessenkool [this message]
2022-03-23 10:31 Martin Liska
-- strict thread matches above, loose matches on Subject: below --
2022-03-23 10:31 Martin Liska
2022-03-23 10:31 Martin Liska
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=20220323111734.GA614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).