public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/58876] No non-virtual-dtor warning in std::unique_ptr Date: Wed, 25 Jun 2014 09:28:00 -0000 [thread overview] Message-ID: <bug-58876-4-Pe7Wmh949j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58876-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58876 Bug 58876 depends on bug 61600, which changed state. Bug 61600 Summary: #pragma GCC diagnostic pop leaves warnings enabled https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61600 What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
next prev parent reply other threads:[~2014-06-25 9:28 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-58876-4@http.gcc.gnu.org/bugzilla/> 2013-10-30 15:04 ` redi at gcc dot gnu.org 2013-10-30 17:57 ` paolo.carlini at oracle dot com 2013-10-30 18:00 ` redi at gcc dot gnu.org 2013-10-30 18:00 ` redi at gcc dot gnu.org 2014-06-25 9:28 ` redi at gcc dot gnu.org [this message] 2014-12-23 23:43 ` mw_triad at users dot sourceforge.net 2014-12-24 9:01 ` redi at gcc dot gnu.org 2014-12-24 16:59 ` mw_triad at users dot sourceforge.net 2014-12-24 20:08 ` redi at gcc dot gnu.org 2014-12-26 16:31 ` mw_triad at users dot sourceforge.net 2021-04-17 10:23 ` db0451 at gmail dot com 2021-04-19 10:40 ` redi at gcc dot gnu.org 2021-08-31 18:20 ` redi at gcc dot gnu.org 2021-08-31 20:09 ` harald at gigawatt dot nl 2021-09-01 9:57 ` redi at gcc dot gnu.org 2024-08-21 13:36 ` redi at gcc dot gnu.org 2024-08-27 16:06 ` redi at gcc dot gnu.org
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=bug-58876-4-Pe7Wmh949j@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).