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/113373] [14 regression] ICE in verify_ssa since r14-6822
Date: Mon, 22 Jan 2024 07:50:19 +0000	[thread overview]
Message-ID: <bug-113373-4-HVgi8nzRDx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113373-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC 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:86f3cbdaa6f60eaff1cdb4ab2f1a9bc796b67207

commit r14-8330-g86f3cbdaa6f60eaff1cdb4ab2f1a9bc796b67207
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Jan 19 13:55:09 2024 +0100

    tree-optimization/113373 - add missing LC PHIs for live operations

    The following makes reduction epilogue code generation happy by properly
    adding LC PHIs to the exit blocks for multiple exit vectorized loops.

    Some refactoring might make the flow easier to follow but I've refrained
    from doing that with this patch.

    I've kept some fixes in reduction epilogue generation from the earlier
    attempt fixing this PR.

            PR tree-optimization/113373
            * tree-vect-loop-manip.cc (slpeel_tree_duplicate_loop_to_edge_cfg):
            Create LC PHIs in the exit blocks where necessary.
            * tree-vect-loop.cc (vectorizable_live_operation): Do not try
            to handle missing LC PHIs.
            (find_connected_edge): Remove.
            (vect_create_epilog_for_reduction): Cleanup use of auto_vec.

            * gcc.dg/vect/vect-early-break_104-pr113373.c: New testcase.

  parent reply	other threads:[~2024-01-22  7:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13  9:43 [Bug c++/113373] New: ice in verify_ssa dcb314 at hotmail dot com
2024-01-13 14:47 ` [Bug tree-optimization/113373] [14 regression] ICE " dcb314 at hotmail dot com
2024-01-13 21:22 ` dcb314 at hotmail dot com
2024-01-13 21:27 ` pinskia at gcc dot gnu.org
2024-01-13 21:45 ` dcb314 at hotmail dot com
2024-01-13 22:56 ` pinskia at gcc dot gnu.org
2024-01-13 22:56 ` pinskia at gcc dot gnu.org
2024-01-15  8:32 ` rguenth at gcc dot gnu.org
2024-01-15  8:49 ` [Bug tree-optimization/113373] [14 regression] ICE in verify_ssa since r14-6822 jakub at gcc dot gnu.org
2024-01-16 13:57 ` rguenth at gcc dot gnu.org
2024-01-22  7:50 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-22  7:50 ` 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-113373-4-HVgi8nzRDx@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).