public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66487] sanitizer/warnings for lifetime DSE Date: Wed, 28 Feb 2024 08:02:38 +0000 [thread overview] Message-ID: <bug-66487-4-Pb69N0KbJQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66487-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66487 --- Comment #28 from Alexander Monakov <amonakov at gcc dot gnu.org> --- The bug is about the issue of lacking diagnostics, it should be fine to make note of various approaches to remedy the problem in one bug report. (in any case, all discussion of the Valgrind-based approach happened on the gcc-patches mailing list, not here)
next prev parent reply other threads:[~2024-02-28 8:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-10 13:09 [Bug c++/66487] New: [6 Regression] Firefox segfault with LTO enabled marxin at gcc dot gnu.org 2015-06-10 13:23 ` [Bug c++/66487] " rguenth at gcc dot gnu.org 2015-06-10 17:55 ` jason at gcc dot gnu.org 2015-06-11 15:57 ` jason at gcc dot gnu.org 2023-08-31 23:07 ` [Bug c++/66487] sanitizer/warnings for lifetime DSE egallager at gcc dot gnu.org 2023-10-30 7:20 ` amonakov at gcc dot gnu.org 2024-02-27 22:20 ` egallager at gcc dot gnu.org 2024-02-28 8:02 ` amonakov at gcc dot gnu.org [this message] 2024-03-30 17:44 ` egallager at gcc dot gnu.org 2024-03-30 17:50 ` egallager 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-66487-4-Pb69N0KbJQ@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).