public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Yong <jyong@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3080] testsuite: Windows reports errors with CreateProcess
Date: Wed,  5 Oct 2022 09:47:11 +0000 (GMT)	[thread overview]
Message-ID: <20221005094711.6EDDB3858029@sourceware.org> (raw)

https://gcc.gnu.org/g:fa8e3a055a082e38aeab2561a5016b01ebfd6ebd

commit r13-3080-gfa8e3a055a082e38aeab2561a5016b01ebfd6ebd
Author: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
Date:   Thu Sep 29 20:07:11 2022 +0200

    testsuite: Windows reports errors with CreateProcess
    
    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>
    Signed-off-by: Jonathan Yong <10walls@gmail.com>

Diff:
---
 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" }

                 reply	other threads:[~2022-10-05  9:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221005094711.6EDDB3858029@sourceware.org \
    --to=jyong@gcc.gnu.org \
    --cc=gcc-cvs@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).