public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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: Fri, 01 Dec 2023 07:41:38 +0000	[thread overview]
Message-ID: <bug-112793-4-M1s86XFioZ@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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
   Target Milestone|---                         |14.0

--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed, mine.  We're scheduling the same SLP node twice from different SLP
instances.  We're supposed to merge SLP instances which share nodes though,
but we're only doing that for internal defs.  We need to either duplicate
the constant/external nodes in different subgraphs or merge subgraphs
with common constants/externals as well.

I'll think about it.

This isn't new in GCC 14, it should be a problem since GCC 11.

  parent reply	other threads:[~2023-12-01  7:41 UTC|newest]

Thread overview: 17+ 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 [this message]
2023-12-14 15:08 ` cvs-commit at gcc dot gnu.org
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

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-M1s86XFioZ@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).