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/112793] [14 regression] ICE when building stellarium (internal compiler error: in vect_schedule_slp_node, at tree-vect-slp.cc:9062)
Date: Thu, 14 Dec 2023 15:08:39 +0000 [thread overview]
Message-ID: <bug-112793-4-zDFclXyeHO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112793-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112793
--- Comment #13 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:d782ec8362eadc3169286eb1e39c631effd02323
commit r14-6550-gd782ec8362eadc3169286eb1e39c631effd02323
Author: Richard Biener <rguenther@suse.de>
Date: Wed Dec 13 14:23:31 2023 +0100
tree-optimization/112793 - SLP of constant/external code-generated twice
The following makes the attempt at code-generating a constant/external
SLP node twice well-formed as that can happen when partitioning BB
vectorization attempts where we keep constants/externals unpartitioned.
PR tree-optimization/112793
* tree-vect-slp.cc (vect_schedule_slp_node): Already
code-generated constant/external nodes are OK.
* g++.dg/vect/pr112793.cc: New testcase.
next prev parent reply other threads:[~2023-12-14 15:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 22:49 [Bug c++/112793] New: " sjames at gcc dot gnu.org
2023-11-30 22:51 ` [Bug tree-optimization/112793] " pinskia at gcc dot gnu.org
2023-11-30 22:52 ` pinskia at gcc dot gnu.org
2023-11-30 22:53 ` sjames at gcc dot gnu.org
2023-11-30 22:54 ` pinskia at gcc dot gnu.org
2023-12-01 3:14 ` sjames at gcc dot gnu.org
2023-12-01 3:27 ` pinskia at gcc dot gnu.org
2023-12-01 3:28 ` pinskia at gcc dot gnu.org
2023-12-01 4:14 ` pinskia at gcc dot gnu.org
2023-12-01 4:14 ` pinskia at gcc dot gnu.org
2023-12-01 6:26 ` pinskia at gcc dot gnu.org
2023-12-01 7:30 ` sjames at gcc dot gnu.org
2023-12-01 7:41 ` rguenth at gcc dot gnu.org
2023-12-14 15:08 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-14 15:10 ` [Bug tree-optimization/112793] [11/12/13 " rguenth at gcc dot gnu.org
2024-03-21 13:54 ` cvs-commit at gcc dot gnu.org
2024-05-17 11:11 ` [Bug tree-optimization/112793] [11/12 " cvs-commit at gcc dot gnu.org
2024-06-21 9:22 ` [Bug tree-optimization/112793] [11 " cvs-commit at gcc dot gnu.org
2024-06-21 9:36 ` 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-112793-4-zDFclXyeHO@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).