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/97886] [11 Regression] ICE in vect_slp_analyze_node_operations, at tree-vect-slp.c:3528 since r11-4428-g4a369d199bf2f34e037030b18d0da923e8a24997 Date: Wed, 18 Nov 2020 09:30:57 +0000 [thread overview] Message-ID: <bug-97886-4-CMdZbrDhjc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97886-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97886 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 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Mine. This is odd IL - we're having a PHI node copying an extern and we're getting confused about it pr95295-3.c:7:6: note: node 0x399c5a0 (max_nunits=16, refcnt=1) pr95295-3.c:7:6: note: stmt 0 arr_2_I_lsm.9_41 = PHI <_4(31)> pr95295-3.c:7:6: note: children 0x399c450 pr95295-3.c:7:6: note: node (external) 0x399c450 (max_nunits=1, refcnt=1) pr95295-3.c:7:6: note: { _4 } of course I never thought we'll run into this ;)
next prev parent reply other threads:[~2020-11-18 9:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-18 9:08 [Bug tree-optimization/97886] New: " marxin at gcc dot gnu.org 2020-11-18 9:08 ` [Bug tree-optimization/97886] " marxin at gcc dot gnu.org 2020-11-18 9:30 ` rguenth at gcc dot gnu.org [this message] 2020-11-18 10:25 ` cvs-commit at gcc dot gnu.org 2020-11-18 10:25 ` 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-97886-4-CMdZbrDhjc@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: linkBe 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).