public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100349] [11/12 Regression] ICE Segmentation fault during GIMPLE pass: evrp (under -O2 to -Os) Date: Mon, 17 May 2021 16:19:51 +0000 [thread overview] Message-ID: <bug-100349-4-wsejTp1J80@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100349-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100349 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:ce81282261c6c77883b17d0ebfbbe337bed76457 commit r12-842-gce81282261c6c77883b17d0ebfbbe337bed76457 Author: Aldy Hernandez <aldyh@redhat.com> Date: Thu May 13 16:09:58 2021 -0400 Bail in bounds_of_var_in_loop if scev returns NULL. Both initial_condition_in_loop_num and evolution_part_in_loop_num can return NULL. This patch exits if either one is NULL. Presumably this didn't happen before, because adjust_range_with_scev was called far less frequently than in ranger, which can call it for every PHI. gcc/ChangeLog: PR tree-optimization/100349 * vr-values.c (bounds_of_var_in_loop): Bail if scev returns NULL. gcc/testsuite/ChangeLog: * gcc.dg/pr100349.c: New test.
next prev parent reply other threads:[~2021-05-17 16:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-30 8:26 [Bug tree-optimization/100349] New: " haoxintu at gmail dot com 2021-04-30 12:01 ` [Bug tree-optimization/100349] " rguenth at gcc dot gnu.org 2021-04-30 14:35 ` aldyh at gcc dot gnu.org 2021-05-13 0:06 ` tlwang at uwaterloo dot ca 2021-05-14 20:17 ` aldyh at gcc dot gnu.org 2021-05-17 16:19 ` cvs-commit at gcc dot gnu.org [this message] 2021-07-16 14:11 ` [Bug tree-optimization/100349] [11 " amacleod at redhat dot com
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-100349-4-wsejTp1J80@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).