From: "François Dumont" <frs.dumont@gmail.com>
To: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH][_GLIBCXX_INLINE_VERSION] Fix test dg-prune-output
Date: Wed, 14 Sep 2022 19:26:16 +0200 [thread overview]
Message-ID: <99765d4f-2ac6-5877-69b6-1bd8684c20ff@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
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.
With this patch all tests are Ok in _GLIBCXX_INLINE_VERSION mode (at the
time I'm writing this).
Ok to commit ?
François
[-- Attachment #2: dg-prune-output.patch --]
[-- Type: text/x-patch, Size: 735 bytes --]
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.
next reply other threads:[~2022-09-14 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:26 François Dumont [this message]
2022-09-15 14:12 ` Jonathan Wakely
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=99765d4f-2ac6-5877-69b6-1bd8684c20ff@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).