From: Jeff Law <jeffreyalaw@gmail.com>
To: Christophe Lyon <christophe.lyon@foss.st.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Remove .exe suffix in prune_gcc_output
Date: Sun, 19 Sep 2021 08:46:45 -0600 [thread overview]
Message-ID: <2f90c1c1-4d44-cde4-0b7b-a53b78b3e193@gmail.com> (raw)
In-Reply-To: <20210908084956.1444294-1-christophe.lyon@foss.st.com>
On 9/8/2021 2:49 AM, Christophe Lyon via Gcc-patches wrote:
> When running the testsuite under Windows, we noticed failures in
> testcase which attempt to match compiler error messages containing the
> name of the executable.
>
> For instance, gcc.dg/analyzer/signal-4a.c tries to match 'cc1:' which
> obviously fails when the executable is called cc1.exe.
>
> This patch removes the .exe suffix from various toolchain executables
> to avoid this problem.
>
> 2021-09-08 Christophe Lyon <christophe.lyon@foss.st.com>
> Torbjörn SVENSSON <torbjorn.svensson@st.com>
>
> gcc/testsuite/
> * lib/prune.exp (prune_gcc_output): Remove .exe suffix from
> toolchain executables names.
OK
jeff
prev parent reply other threads:[~2021-09-19 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:49 Christophe Lyon
2021-09-13 8:31 ` Christophe LYON
2021-09-19 14:46 ` 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=2f90c1c1-4d44-cde4-0b7b-a53b78b3e193@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=christophe.lyon@foss.st.com \
--cc=gcc-patches@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).