From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <ro@CeBiTec.Uni-Bielefeld.DE>, <mikestump@comcast.net>,
Yvan ROUX <yvan.roux@foss.st.com>, <richard.earnshaw@arm.com>
Subject: PING^1 [PATCH] testsuite: Windows reports errors with CreateProcess
Date: Wed, 5 Oct 2022 11:15:06 +0200 [thread overview]
Message-ID: <0e9221ed-9709-9dc5-532d-d4f637314dfb@foss.st.com> (raw)
In-Reply-To: <20220929180710.2235253-1-torbjorn.svensson@foss.st.com>
Hi,
Ping, https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602541.html
Kind regards,
Torbjörn
On 2022-09-29 20:07, Torbjörn SVENSSON wrote:
> When the mapper can't be executed, Windows report the error like:
> .../bad-mapper-1.C: error: failed CreateProcess mapper 'this-will-not-work'
>
> On Linux, the same error is reported this way:
> .../bad-mapper-1.C: error: failed execvp mapper 'this-will-not-work'
>
> This patch allows both output forms to be accepted.
>
> Patch has been verified on Windows and Linux.
>
> gcc/testsuite:
>
> * g++.dg/modules/bad-mapper-1.C: Also accept CreateProcess.
>
> Co-Authored-By: Yvan ROUX <yvan.roux@foss.st.com>
> Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
> ---
> gcc/testsuite/g++.dg/modules/bad-mapper-1.C | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/g++.dg/modules/bad-mapper-1.C b/gcc/testsuite/g++.dg/modules/bad-mapper-1.C
> index 6d0ed4b5895..4b2312885d8 100644
> --- a/gcc/testsuite/g++.dg/modules/bad-mapper-1.C
> +++ b/gcc/testsuite/g++.dg/modules/bad-mapper-1.C
> @@ -1,6 +1,6 @@
> // { dg-additional-options "-fmodules-ts -fmodule-mapper=|this-will-not-work" }
> import unique1.bob;
> -// { dg-error "-:failed exec.*mapper.* .*this-will-not-work" "" { target { ! { *-*-darwin[89]* *-*-darwin10* } } } 0 }
> +// { dg-error "-:failed (exec|CreateProcess).*mapper.* .*this-will-not-work" "" { target { ! { *-*-darwin[89]* *-*-darwin10* } } } 0 }
> // { dg-prune-output "fatal error:" }
> // { dg-prune-output "failed to read" }
> // { dg-prune-output "compilation terminated" }
next prev parent reply other threads:[~2022-10-05 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 18:07 Torbjörn SVENSSON
2022-10-05 9:15 ` Torbjorn SVENSSON [this message]
2022-10-05 9:48 ` PING^1 " Jonathan Yong
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=0e9221ed-9709-9dc5-532d-d4f637314dfb@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=richard.earnshaw@arm.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=yvan.roux@foss.st.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).