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/108970] [13 Regression] ICE in vect_do_peeling, at tree-vect-loop-manip.cc:2971, or ICE in dump_printf_loc, at dumpfile.cc:1359
Date: Wed, 01 Mar 2023 09:10:10 +0000	[thread overview]
Message-ID: <bug-108970-4-CdVCFDhiRr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108970-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:85203d52bfa4a84da5f50e0a242891308ffa8d83

commit r13-6386-g85203d52bfa4a84da5f50e0a242891308ffa8d83
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Mar 1 09:10:19 2023 +0100

    tree-optimization/108970 - ICE with vectorizer peeling

    The function slpeel_can_duplicate_loop_p fails to verify we can
    copy blocks, instead slpeel_tree_duplicate_loop_to_edge_cfg does
    but that's too late.  The following fixes this, also simplifying
    error reporting which is somewhat pointless if we ICE immediately.

            PR tree-optimization/108970
            * tree-vect-loop-manip.cc (slpeel_can_duplicate_loop_p):
            Check we can copy the BBs.
            (slpeel_tree_duplicate_loop_to_edge_cfg): Avoid redundant
            check.
            (vect_do_peeling): Streamline error handling.

            * gcc.dg/pr108970.c: New testcase.

  parent reply	other threads:[~2023-03-01  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 16:47 [Bug tree-optimization/108970] New: " asolokha at gmx dot com
2023-02-28 16:50 ` [Bug tree-optimization/108970] " pinskia at gcc dot gnu.org
2023-03-01  7:42 ` rguenth at gcc dot gnu.org
2023-03-01  9:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-01  9: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-108970-4-CdVCFDhiRr@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).