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/111009] [12/13 regression] -fno-strict-overflow erroneously elides null pointer checks and causes SIGSEGV on perf from linux-6.4.10 Date: Wed, 08 May 2024 12:03:12 +0000 [thread overview] Message-ID: <bug-111009-4-V0PKG8Raqq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111009 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |amacleod at redhat dot com Status|NEW |ASSIGNED --- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> --- Andrew - this doesn't pick to gcc-13 because of the following but we should backport the fix somehow. Can you please see to that in time for GCC 13.3 (next week)? /space/rguenther/src/gcc-13-branch/gcc/range-op.cc: In member function ‘virtual bool operator_addr_expr::op1_range(irange&, tree, const irange&, const irange&, relation_trio) const’: /space/rguenther/src/gcc-13-branch/gcc/range-op.cc:4366:8: error: ‘contains_zero_p’ was not declared in this scope if (!contains_zero_p (lhs) && TYPE_OVERFLOW_UNDEFINED (type)) ^~~~~~~~~~~~~~~ /space/rguenther/src/gcc-13-branch/gcc/range-op.cc:4366:8: note: suggested alternative: ‘contains_mem_rtx_p’ if (!contains_zero_p (lhs) && TYPE_OVERFLOW_UNDEFINED (type)) ^~~~~~~~~~~~~~~ contains_mem_rtx_p
next prev parent reply other threads:[~2024-05-08 12:03 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-14 8:26 [Bug middle-end/111009] New: [12/13/14 " slyfox at gcc dot gnu.org 2023-08-14 9:34 ` [Bug middle-end/111009] " amonakov at gcc dot gnu.org 2023-08-14 11:34 ` rguenth at gcc dot gnu.org 2023-08-14 11:48 ` rguenth at gcc dot gnu.org 2023-08-15 17:57 ` amacleod at redhat dot com 2023-08-16 20:14 ` slyfox at gcc dot gnu.org 2023-08-16 20:21 ` sjames at gcc dot gnu.org 2023-08-16 20:40 ` slyfox at gcc dot gnu.org 2023-08-16 21:05 ` amacleod at redhat dot com 2023-08-16 21:24 ` slyfox at gcc dot gnu.org 2023-08-17 15:37 ` amacleod at redhat dot com 2023-08-17 17:39 ` cvs-commit at gcc dot gnu.org 2023-08-17 19:44 ` slyfox at gcc dot gnu.org 2024-05-08 12:03 ` rguenth at gcc dot gnu.org [this message] 2024-05-08 18:26 ` [Bug middle-end/111009] [12/13 " amacleod at redhat dot com 2024-05-09 14:32 ` cvs-commit at gcc dot gnu.org 2024-05-10 6:36 ` [Bug middle-end/111009] [12 " rguenth at gcc dot gnu.org 2024-05-13 17:49 ` cvs-commit at gcc dot gnu.org 2024-06-12 11:38 ` 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-111009-4-V0PKG8Raqq@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).