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/114231] [12/13 Regression] ICE when building libjxl
Date: Thu, 21 Mar 2024 13:54:36 +0000	[thread overview]
Message-ID: <bug-114231-4-kAL7vJn4wZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114231-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:04fffbaa87997ac893a9aa68b674c938ba3ecddb

commit r13-8486-g04fffbaa87997ac893a9aa68b674c938ba3ecddb
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Mar 5 10:55:56 2024 +0100

    tree-optimization/114231 - use patterns for BB SLP discovery root stmts

    The following makes sure to use recognized patterns when vectorizing
    roots during BB SLP discovery.  We need to apply those late since
    during root discovery we've not yet done pattern recognition.
    All parts of the vectorizer assume patterns get used, for the testcase
    we mix this up when doing live lane computation.

            PR tree-optimization/114231
            * tree-vect-slp.cc (vect_analyze_slp): Lookup patterns when
            processing a BB SLP root.

            * gcc.dg/vect/pr114231.c: New testcase.

  parent reply	other threads:[~2024-03-21 13:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  5:11 [Bug tree-optimization/114231] New: [14 regression] " sjames at gcc dot gnu.org
2024-03-05  5:11 ` [Bug tree-optimization/114231] " sjames at gcc dot gnu.org
2024-03-05  5:15 ` pinskia at gcc dot gnu.org
2024-03-05  5:16 ` sjames at gcc dot gnu.org
2024-03-05  5:22 ` pinskia at gcc dot gnu.org
2024-03-05  5:33 ` pinskia at gcc dot gnu.org
2024-03-05  5:41 ` pinskia at gcc dot gnu.org
2024-03-05  5:49 ` pinskia at gcc dot gnu.org
2024-03-05  5:54 ` [Bug tree-optimization/114231] [12/13/14 " pinskia at gcc dot gnu.org
2024-03-05  6:11 ` pinskia at gcc dot gnu.org
2024-03-05  6:20 ` pinskia at gcc dot gnu.org
2024-03-05  7:31 ` jakub at gcc dot gnu.org
2024-03-05  8:56 ` rguenth at gcc dot gnu.org
2024-03-05  9:54 ` rguenth at gcc dot gnu.org
2024-03-05 10:47 ` cvs-commit at gcc dot gnu.org
2024-03-05 10:53 ` [Bug tree-optimization/114231] [12/13 Regression] " rguenth at gcc dot gnu.org
2024-03-21 13:54 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-21 13:55 ` [Bug tree-optimization/114231] [12 " rguenth at gcc dot gnu.org
2024-05-16  9:56 ` cvs-commit at gcc dot gnu.org
2024-05-16 10:39 ` 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-114231-4-kAL7vJn4wZ@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).