public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r12-5533] libstdc++: Remove dg-error that no longer happens
Date: Thu, 25 Nov 2021 23:12:33 +0000 (GMT)	[thread overview]
Message-ID: <20211125231233.1E91C3858002@sourceware.org> (raw)

https://gcc.gnu.org/g:9664c46545601728698a6e3352b32ffcf9a4ade7

commit r12-5533-g9664c46545601728698a6e3352b32ffcf9a4ade7
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Nov 25 22:54:07 2021 +0000

    libstdc++: Remove dg-error that no longer happens
    
    There was a c++11_only dg-error in this testcase, for a "body of
    constexpr function is not a return statement" diagnostic that was bogus,
    but happened because the return statement was ill-formed. A change to
    G++ earlier this month means that diagnostic is no longer emitted, so
    remove the dg-error.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/20_util/tuple/comparison_operators/overloaded2.cc:
            Remove dg-error for C++11_only error.

Diff:
---
 libstdc++-v3/testsuite/20_util/tuple/comparison_operators/overloaded2.cc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/20_util/tuple/comparison_operators/overloaded2.cc b/libstdc++-v3/testsuite/20_util/tuple/comparison_operators/overloaded2.cc
index bac16ffd521..6a7a584c71e 100644
--- a/libstdc++-v3/testsuite/20_util/tuple/comparison_operators/overloaded2.cc
+++ b/libstdc++-v3/testsuite/20_util/tuple/comparison_operators/overloaded2.cc
@@ -52,4 +52,3 @@ auto b = a < a;
 // { dg-error "no match for 'operator<'" "" { target c++20 } 0 }
 // { dg-error "no match for .*_Synth3way|in requirements" "" { target c++20 } 0 }
 // { dg-error "ordered comparison" "" { target c++17_down } 0 }
-// { dg-error "not a return-statement" "" { target c++11_only } 0 }


                 reply	other threads:[~2021-11-25 23:12 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=20211125231233.1E91C3858002@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-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).