From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>,
Brendan Shanks <bshanks@codeweavers.com>
Cc: gcc-patches@gcc.gnu.org, prathamesh.kulkarni@linaro.org,
patrick@rivosinc.com
Subject: Re: [PATCH] testsuite: Fix bad-mapper-1.C test failures with posix_spawn
Date: Mon, 13 Nov 2023 11:48:09 -0700 [thread overview]
Message-ID: <e5754f51-2792-4d5b-9d53-71e08d7507fd@gmail.com> (raw)
In-Reply-To: <CAFiYyc21HdJ=yZpAAHFxrzGwwPmYGotHsjyhU=azFWKx5XAxOw@mail.gmail.com>
On 11/12/23 23:53, Richard Biener wrote:
> On Sun, Nov 12, 2023 at 12:12 AM Brendan Shanks <bshanks@codeweavers.com> wrote:
>>
>> bad-mapper-1.C has been failing since the posix_spawn codepath was added
>> to libiberty, adjust the check to accept the changed error message.
>>
>> Patch has been verified on x86_64 Linux.
>
> OK
And pushed to the trunk. I'd also checked it on ppc64le :-)
jeff
prev parent reply other threads:[~2023-11-13 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 23:11 Brendan Shanks
2023-11-13 6:53 ` Richard Biener
2023-11-13 18:48 ` Jeff Law [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=e5754f51-2792-4d5b-9d53-71e08d7507fd@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=bshanks@codeweavers.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=patrick@rivosinc.com \
--cc=prathamesh.kulkarni@linaro.org \
--cc=richard.guenther@gmail.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).