public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: "Franथईois Dumont" <fdumont@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-2686] libstdc++: [_GLIBCXX_INLINE_VERSION] Fix test dg-prune-output
Date: Thu, 15 Sep 2022 17:01:21 +0000 (GMT)	[thread overview]
Message-ID: <20220915170121.758CA381DC56@sourceware.org> (raw)

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

commit r13-2686-gdb58fa0b053327acfa42fbe6ca673e6eddd7852b
Author: François Dumont <fdumont@gcc.gnu.org>
Date:   Wed Sep 14 19:14:48 2022 +0200

    libstdc++: [_GLIBCXX_INLINE_VERSION] Fix test dg-prune-output
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/20_util/is_complete_or_unbounded/memoization_neg.cc:
            Adapt dg-prune-output to _GLIBCXX_INLINE_VERSION mode.

Diff:
---
 .../testsuite/20_util/is_complete_or_unbounded/memoization_neg.cc       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/20_util/is_complete_or_unbounded/memoization_neg.cc b/libstdc++-v3/testsuite/20_util/is_complete_or_unbounded/memoization_neg.cc
index fc0b70b319c..bc66c13feee 100644
--- a/libstdc++-v3/testsuite/20_util/is_complete_or_unbounded/memoization_neg.cc
+++ b/libstdc++-v3/testsuite/20_util/is_complete_or_unbounded/memoization_neg.cc
@@ -1,6 +1,6 @@
 // { dg-do compile { target c++11 } }
 // { dg-prune-output "must be a complete" }
-// { dg-prune-output "'value' is not a member of 'std::is_move_cons" }
+// { dg-prune-output "'value' is not a member of 'std::(__8::)?is_move_cons" }
 // { dg-prune-output "invalid use of incomplete type" }
 
 // Copyright (C) 2019-2022 Free Software Foundation, Inc.

                 reply	other threads:[~2022-09-15 17:01 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=20220915170121.758CA381DC56@sourceware.org \
    --to=fdumont@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).