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/99947] [11 Regression] ICE Segmentation fault "during GIMPLE pass: vect" since r11-4714-g092cdbd919849759 Date: Wed, 07 Apr 2021 07:54:27 +0000 [thread overview] Message-ID: <bug-99947-4-8Kva5lvaCQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99947-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99947 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Meh. C++. vec_steps.safe_push (vec_steps[0]); breaks when vec_steps.safe_push re-allocates (vec_steps[0] returns a reference). Testing a fix.
next prev parent reply other threads:[~2021-04-07 7:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-07 2:11 [Bug tree-optimization/99947] New: [11 Regression] ICE Segmentation fault "during GIMPLE pass: vect" haoxintu at gmail dot com 2021-04-07 6:11 ` [Bug tree-optimization/99947] [11 Regression] ICE Segmentation fault "during GIMPLE pass: vect" since r11-4714-g092cdbd919849759 marxin at gcc dot gnu.org 2021-04-07 7:37 ` rguenth at gcc dot gnu.org 2021-04-07 7:40 ` marxin at gcc dot gnu.org 2021-04-07 7:54 ` rguenth at gcc dot gnu.org [this message] 2021-04-07 8:51 ` cvs-commit at gcc dot gnu.org 2021-04-07 8:52 ` rguenth at gcc dot gnu.org 2021-04-07 9:20 ` haoxintu at gmail dot com
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-99947-4-8Kva5lvaCQ@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).