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/103219] [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) since r12-4526-gd8edfadfc7a9795b
Date: Mon, 15 Nov 2021 10:10:36 +0000	[thread overview]
Message-ID: <bug-103219-4-fKTbSjIfwX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103219-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103219

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:d1ca8aeaf34a717dffd8f4a1f0333d25c7d1c904

commit r12-5264-gd1ca8aeaf34a717dffd8f4a1f0333d25c7d1c904
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Nov 15 11:07:55 2021 +0100

    tree-optimization/103219 - avoid ICE in unroll-and-jam

    For no particularly good reason unroll-and-jam uses single_dom_exit
    to determine the exit for the region it wants to run VN on.  That
    happens to ICE because of the dominance restriction.  Use single_exit
    instead.

    2021-11-15  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/103219
            * gimple-loop-jam.c (tree_loop_unroll_and_jam): Use single_exit
            to determine the exit for the VN region.

            * gcc.dg/torture/pr103219.c: New testcase.

  parent reply	other threads:[~2021-11-15 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13  2:21 [Bug tree-optimization/103219] New: [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) haoxintu at gmail dot com
2021-11-13  2:26 ` [Bug tree-optimization/103219] " pinskia at gcc dot gnu.org
2021-11-14 10:25 ` [Bug tree-optimization/103219] [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) since r12-4526-gd8edfadfc7a9795b aldyh at gcc dot gnu.org
2021-11-14 22:03 ` pinskia at gcc dot gnu.org
2021-11-15  8:57 ` rguenth at gcc dot gnu.org
2021-11-15 10:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-15 10:11 ` [Bug tree-optimization/103219] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-02-17  8:20 ` [Bug tree-optimization/103219] [12 " 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-103219-4-fKTbSjIfwX@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: link
Be 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).