public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110055] [13 Regression] Dangling pointer warning inside std::vector on RISC-V Date: Tue, 06 Jun 2023 08:41:41 +0000 [thread overview] Message-ID: <bug-110055-4-wM40iQkTKV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110055-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110055 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org Priority|P3 |P2 Summary|Dangling pointer warning |[13 Regression] Dangling |inside std::vector on |pointer warning inside |RISC-V |std::vector on RISC-V Target Milestone|--- |13.2 --- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed on trunk, introduced with r0-113304-gd0ad58f94e22dc so it's a regression (but this seems to be the first discovered fallout). I'm queuing backports for GCC 13 only sofar.
next prev parent reply other threads:[~2023-06-06 8:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 10:03 [Bug c++/110055] New: " spriteovo at gmail dot com 2023-05-31 10:05 ` [Bug c++/110055] " spriteovo at gmail dot com 2023-05-31 13:32 ` spriteovo at gmail dot com 2023-05-31 23:46 ` [Bug middle-end/110055] " pinskia at gcc dot gnu.org 2023-05-31 23:47 ` pinskia at gcc dot gnu.org 2023-06-01 0:07 ` pinskia at gcc dot gnu.org 2023-06-02 7:13 ` rguenth at gcc dot gnu.org 2023-06-02 7:25 ` rguenth at gcc dot gnu.org 2023-06-05 11:15 ` spriteovo at gmail dot com 2023-06-06 8:30 ` cvs-commit at gcc dot gnu.org 2023-06-06 8:41 ` rguenth at gcc dot gnu.org [this message] 2023-06-23 10:30 ` [Bug middle-end/110055] [13 Regression] " cvs-commit at gcc dot gnu.org 2023-06-23 10:30 ` rguenth 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-110055-4-wM40iQkTKV@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).