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 tree-optimization/79334] Segfault on tree loop hoisting Date: Mon, 23 Aug 2021 08:00:08 +0000 [thread overview] Message-ID: <bug-79334-4-e6mxPiw9vJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-79334-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79334 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- So this should now be correctly checked after g:fedcf3c476aff7533741a1c61071200f0a38cf83 which fixes prune_clobbered_mems. That uses vn_reference_may_trap which only does case ARRAY_RANGE_REF: case ARRAY_REF: if (TREE_CODE (op->op0) == SSA_NAME) return true; so doesn't return true for out-of-bound reads. tree_could_trap_p uses [range_]in_array_bounds_p which we'd need to replicate here. I'm testing a patch.
next prev parent reply other threads:[~2021-08-23 8:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-79334-4@http.gcc.gnu.org/bugzilla/> 2021-08-22 20:38 ` pinskia at gcc dot gnu.org 2021-08-23 8:00 ` rguenth at gcc dot gnu.org [this message] 2021-08-23 9:53 ` cvs-commit at gcc dot gnu.org 2021-08-23 9:54 ` 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-79334-4-e6mxPiw9vJ@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).