From: Christophe LYON <christophe.lyon@foss.st.com>
To: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] testsuite: Remove .exe suffix in prune_gcc_output
Date: Mon, 13 Sep 2021 10:31:13 +0200 [thread overview]
Message-ID: <72613a92-9846-6555-5e65-d1fc0b6d588a@foss.st.com> (raw)
In-Reply-To: <20210908084956.1444294-1-christophe.lyon@foss.st.com>
ping?
On 08/09/2021 10:49, Christophe Lyon 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.
> ---
> gcc/testsuite/lib/prune.exp | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/gcc/testsuite/lib/prune.exp b/gcc/testsuite/lib/prune.exp
> index 91f165bec38..fac212ecf60 100644
> --- a/gcc/testsuite/lib/prune.exp
> +++ b/gcc/testsuite/lib/prune.exp
> @@ -37,6 +37,9 @@ proc prune_gcc_output { text } {
> # Handle any freeform regexps.
> set text [handle-dg-regexps $text]
>
> + # Remove Windows .exe suffix
> + regsub -all "(as|cc1|cc1plus|collect2|f951|ld|lto-wrapper)\.exe?:" $text {\1:} text
> +
> regsub -all "(^|\n)(\[^\n\]*: \[iI\]|I)n ((static member |lambda )?function|member|method|(copy )?constructor|destructor|instantiation|substitution|program|subroutine|block-data)\[^\n\]*" $text "" text
> regsub -all "(^|\n)\[^\n\]*(: )?At (top level|global scope):\[^\n\]*" $text "" text
> regsub -all "(^|\n)\[^\n\]*: (recursively )?required \[^\n\]*" $text "" text
next prev parent reply other threads:[~2021-09-13 8:31 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 [this message]
2021-09-19 14:46 ` Jeff Law
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=72613a92-9846-6555-5e65-d1fc0b6d588a@foss.st.com \
--to=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).