public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100626] [11/12 Regression] ICE Segmentation fault (during RTL pass: split1) since r11-165-geb72dc663e9070b2
Date: Mon, 17 May 2021 18:37:52 +0000 [thread overview]
Message-ID: <bug-100626-4-6b9H03Z55s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100626-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100626
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
Status|NEW |ASSIGNED
--- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 50828
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50828&action=edit
Proposed patch
Patch in testing.
next prev parent reply other threads:[~2021-05-17 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 18:05 [Bug tree-optimization/100626] New: ICE Segmentation fault (during RTL pass: split1) haoxintu at gmail dot com
2021-05-17 1:54 ` [Bug target/100626] " haoxintu at gmail dot com
2021-05-17 8:08 ` [Bug target/100626] [11/12 Regression] ICE Segmentation fault (during RTL pass: split1) since r11-165-geb72dc663e9070b2 marxin at gcc dot gnu.org
2021-05-17 8:53 ` jakub at gcc dot gnu.org
2021-05-17 11:26 ` ubizjak at gmail dot com
2021-05-17 12:49 ` rguenth at gcc dot gnu.org
2021-05-17 18:09 ` haoxintu at gmail dot com
2021-05-17 18:37 ` ubizjak at gmail dot com [this message]
2021-05-18 13:46 ` cvs-commit at gcc dot gnu.org
2021-05-25 17:22 ` cvs-commit at gcc dot gnu.org
2021-05-25 17:23 ` ubizjak 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-100626-4-6b9H03Z55s@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).