public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Bernd Edlinger <edlinger@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-947] Fix a test failure in g++.dg/modules/omp-1_c.C
Date: Thu, 20 May 2021 18:26:40 +0000 (GMT)	[thread overview]
Message-ID: <20210520182640.B3B0C3857C5F@sourceware.org> (raw)

https://gcc.gnu.org/g:4f4a2f199baf46d35492edadc16f30f32920c4df

commit r12-947-g4f4a2f199baf46d35492edadc16f30f32920c4df
Author: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date:   Thu May 20 20:19:43 2021 +0200

    Fix a test failure in g++.dg/modules/omp-1_c.C
    
    Adjust the line number due to previous commit,
    which added a line for dg-require-effective-target.
    
    2021-05-20  Bernd Edlinger  <bernd.edlinger@hotmail.de>
    
            * g++.dg/modules/omp-1_c.C: Fix testcase.

Diff:
---
 gcc/testsuite/g++.dg/modules/omp-1_c.C | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/g++.dg/modules/omp-1_c.C b/gcc/testsuite/g++.dg/modules/omp-1_c.C
index 599a5a5d34f..71a24f6c8ef 100644
--- a/gcc/testsuite/g++.dg/modules/omp-1_c.C
+++ b/gcc/testsuite/g++.dg/modules/omp-1_c.C
@@ -3,7 +3,7 @@
 
 import foo;
 
-// { dg-regexp "In module imported at \[^\n]*omp-1_c.C:3:1:\nfoo: error: module contains OpenMP, use '-fopenmp' to enable\n" }
+// { dg-regexp "In module imported at \[^\n]*omp-1_c.C:4:1:\nfoo: error: module contains OpenMP, use '-fopenmp' to enable\n" }
 // { dg-prune-output "failed to read" }
 // { dg-prune-output "fatal error:" }
 // { dg-prune-output "compilation terminated" }


                 reply	other threads:[~2021-05-20 18:26 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=20210520182640.B3B0C3857C5F@sourceware.org \
    --to=edlinger@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).