public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5737] testsuite: Fix up PR108525 test [PR108525]
Date: Wed,  8 Feb 2023 12:59:11 +0000 (GMT)	[thread overview]
Message-ID: <20230208125912.03EEF3858D39@sourceware.org> (raw)

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

commit r13-5737-ga58a4a57f9a4445f93b495f776f45e1118777e88
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Feb 8 13:57:00 2023 +0100

    testsuite: Fix up PR108525 test [PR108525]
    
    Seems when committing the PR108525 fix I've missed that a test with
    the same name had been added a few hours before for PR108526.
    
    This patch separates the PR108525 test into a new file.
    
    2023-02-08  Jakub Jelinek  <jakub@redhat.com>
    
            PR c++/108525
            * g++.dg/cpp23/static-operator-call5.C: Move PR108525 testcase
            incorrectly applied into PR108526 testcase ...
            * g++.dg/cpp23/static-operator-call6.C: ... here.  New test.

Diff:
---
 gcc/testsuite/g++.dg/cpp23/static-operator-call5.C | 5 -----
 gcc/testsuite/g++.dg/cpp23/static-operator-call6.C | 5 +++++
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/gcc/testsuite/g++.dg/cpp23/static-operator-call5.C b/gcc/testsuite/g++.dg/cpp23/static-operator-call5.C
index ecbb843ef3c..ae022d0b971 100644
--- a/gcc/testsuite/g++.dg/cpp23/static-operator-call5.C
+++ b/gcc/testsuite/g++.dg/cpp23/static-operator-call5.C
@@ -1,8 +1,3 @@
-// PR c++/108525
-// { dg-do compile { target c++23 } }
-
-auto b = [](...) static { return 1; };
-auto foo () { return b (); }
 // PR c++/108526
 // { dg-do compile { target c++23 } }
 
diff --git a/gcc/testsuite/g++.dg/cpp23/static-operator-call6.C b/gcc/testsuite/g++.dg/cpp23/static-operator-call6.C
new file mode 100644
index 00000000000..c3e4a846a10
--- /dev/null
+++ b/gcc/testsuite/g++.dg/cpp23/static-operator-call6.C
@@ -0,0 +1,5 @@
+// PR c++/108525
+// { dg-do compile { target c++23 } }
+
+auto b = [](...) static { return 1; };
+auto foo () { return b (); }

                 reply	other threads:[~2023-02-08 12:59 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=20230208125912.03EEF3858D39@sourceware.org \
    --to=jakub@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).