From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Use dg-bogus in new test [PR108554]
Date: Fri, 27 Jan 2023 15:44:29 +0000 [thread overview]
Message-ID: <20230127154429.1599859-1-jwakely@redhat.com> (raw)
I messed up my first attempt to use dg-bogus with a typo, so didn't
include it in this new test. But it works if I fix the typo.
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/108554
* testsuite/23_containers/map/modifiers/108554.cc: Use dg-bogus.
---
libstdc++-v3/testsuite/23_containers/map/modifiers/108554.cc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libstdc++-v3/testsuite/23_containers/map/modifiers/108554.cc b/libstdc++-v3/testsuite/23_containers/map/modifiers/108554.cc
index 7076682f4c9..811a479b382 100644
--- a/libstdc++-v3/testsuite/23_containers/map/modifiers/108554.cc
+++ b/libstdc++-v3/testsuite/23_containers/map/modifiers/108554.cc
@@ -4,6 +4,8 @@
// PR libstdc++/108554
// Warning from -Wnull-dereference when extracting a unique_ptr from a map.
+// { dg-bogus "null pointer dereference" "PR 108554" { target *-*-* } 0 }
+
#include <map>
#include <memory>
#include <string>
--
2.39.1
reply other threads:[~2023-01-27 15:44 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=20230127154429.1599859-1-jwakely@redhat.com \
--to=jwakely@redhat.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).