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-3863] libstdc++: Remove c++20-specific dg-error directives in test Date: Thu, 23 Sep 2021 15:08:52 +0000 (GMT) [thread overview] Message-ID: <20210923150852.2D163385803F@sourceware.org> (raw) https://gcc.gnu.org/g:43358e91bd1d2b376ce8f426cf9becedf8343a06 commit r12-3863-g43358e91bd1d2b376ce8f426cf9becedf8343a06 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Sep 22 18:15:24 2021 +0100 libstdc++: Remove c++20-specific dg-error directives in test I added extra dg-error directives for C++20 to match the extra errors caused by some of the call stack being constexpr in C++20. Since Jason's changes to reduce those errors, those dg-error lines no longer match. This removes them again. Signed-off-by: Jonathan Wakely <jwakely@redhat.com> libstdc++-v3/ChangeLog: * testsuite/20_util/specialized_algorithms/memory_management_tools/destroy_neg.cc: Remove dg-error lines for C++20-only errors. Diff: --- .../specialized_algorithms/memory_management_tools/destroy_neg.cc | 2 -- 1 file changed, 2 deletions(-) diff --git a/libstdc++-v3/testsuite/20_util/specialized_algorithms/memory_management_tools/destroy_neg.cc b/libstdc++-v3/testsuite/20_util/specialized_algorithms/memory_management_tools/destroy_neg.cc index e114168842e..dfdead42daa 100644 --- a/libstdc++-v3/testsuite/20_util/specialized_algorithms/memory_management_tools/destroy_neg.cc +++ b/libstdc++-v3/testsuite/20_util/specialized_algorithms/memory_management_tools/destroy_neg.cc @@ -47,5 +47,3 @@ test02() } // { dg-error "value type is destructible" "" { target *-*-* } 0 } -// { dg-error "use of deleted function" "" { target c++20 } 0 } -// { dg-error "is private within this context" "" { target c++20 } 0 }
reply other threads:[~2021-09-23 15:08 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=20210923150852.2D163385803F@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: linkBe 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).