public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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 pragma_misc9.c
Date: Wed, 1 Dec 2021 16:32:59 -0600	[thread overview]
Message-ID: <20211201223259.GJ614@gate.crashing.org> (raw)
In-Reply-To: <2ba31ed8-7403-5f23-dbbb-c8d4924b1872@linux.ibm.com>

On Thu, Nov 18, 2021 at 10:18:06AM -0600, Bill Schmidt wrote:
> Hi!  This patch is broken out from the test suite patch for the new
> builtins support.  This one is just a minor adjustment for the error
> message wording.
> 
> Tested on powerpc64le-linux-gnu and powerpc64-linux-gnu (-m32/-m64)
> with no regressions.  Is this okay for trunk?

Okay.  Thanks!


Segher

      parent reply	other threads:[~2021-12-01 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 16:18 Bill Schmidt
2021-12-01 16:36 ` [PATCH, PING] " Bill Schmidt
2021-12-01 22:32 ` Segher Boessenkool [this message]

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=20211201223259.GJ614@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).