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++/108554] [12 Regression] Warning "null pointer dereferece" raised when extracting a unique_ptr from a map and any "-O" flag Date: Thu, 26 Jan 2023 13:41:53 +0000 [thread overview] Message-ID: <bug-108554-4-T5phZ6zy4I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108554-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108554 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |11.3.0 Known to fail| |12.2.0 Target Milestone|--- |12.3 Summary|Warning "null pointer |[12 Regression] Warning |dereferece" raised when |"null pointer dereferece" |extracting a unique_ptr |raised when extracting a |from a map and any "-O" |unique_ptr from a map and |flag |any "-O" flag --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- Fixed on trunk, but this should be backported to gcc-12 too. The warning is present on older branches but suppressed by default, so it's not important to backport before to older branches.
next prev parent reply other threads:[~2023-01-26 13:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-26 9:13 [Bug libstdc++/108554] New: " fcontact at cuveland dot de 2023-01-26 9:51 ` [Bug libstdc++/108554] " redi at gcc dot gnu.org 2023-01-26 9:56 ` fcontact at cuveland dot de 2023-01-26 10:11 ` redi at gcc dot gnu.org 2023-01-26 10:14 ` redi at gcc dot gnu.org 2023-01-26 13:38 ` cvs-commit at gcc dot gnu.org 2023-01-26 13:41 ` redi at gcc dot gnu.org [this message] 2023-01-27 15:43 ` [Bug libstdc++/108554] [12 Regression] " cvs-commit at gcc dot gnu.org 2023-03-28 23:35 ` cvs-commit at gcc dot gnu.org 2023-03-28 23:35 ` 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-108554-4-T5phZ6zy4I@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).