From: Mike Stump <mikestump@comcast.net>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
Paolo Bonzini <bonzini@gnu.org>,
neroden@gcc.gnu.org, aoliva@gcc.gnu.org, Ralf.Wildenhues@gmx.de
Subject: Re: [PATCH] Allow overriding EXPECT
Date: Thu, 21 Dec 2023 11:43:23 -0800 [thread overview]
Message-ID: <4E705C7A-CAB0-4764-93C5-E1B75757434D@comcast.net> (raw)
In-Reply-To: <20231221164914.943125-1-christophe.lyon@linaro.org>
On Dec 21, 2023, at 8:49 AM, Christophe Lyon <christophe.lyon@linaro.org> wrote:
>
> While investigating possible race conditions in the GCC testsuites
> caused by bufferization issues, I wanted to investigate workarounds
> similar to GDB's READ1 [1], and I noticed it was not always possible
> to override EXPECT when running 'make check'.
>
> This patch adds the missing support in various Makefiles.
Ok.
prev parent reply other threads:[~2023-12-21 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 16:49 Christophe Lyon
2023-12-21 19:43 ` Mike Stump [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=4E705C7A-CAB0-4764-93C5-E1B75757434D@comcast.net \
--to=mikestump@comcast.net \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@gcc.gnu.org \
--cc=bonzini@gnu.org \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=neroden@gcc.gnu.org \
/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).