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/94621] [9/10 Regression] GCC 9.2.1 segfaults when compiling file with -O3 since r9-5354
Date: Fri, 17 Apr 2020 07:00:26 +0000 [thread overview]
Message-ID: <bug-94621-4-X0YZ1p0QDs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94621-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94621
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> Created attachment 48294 [details]
> gcc10-pr94621.patch
>
> Untested fix.
LGTM (obvious even)
next prev parent reply other threads:[~2020-04-17 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 15:03 [Bug c/94621] New: GCC 9.2.1 segfaults when compiling file with -O3 ola.olsson at acconeer dot com
2020-04-16 15:04 ` [Bug c/94621] " ola.olsson at acconeer dot com
2020-04-16 15:08 ` jakub at gcc dot gnu.org
2020-04-16 15:53 ` [Bug tree-optimization/94621] [9/10 Regression] GCC 9.2.1 segfaults when compiling file with -O3 since r9-5354 jakub at gcc dot gnu.org
2020-04-16 16:31 ` jakub at gcc dot gnu.org
2020-04-16 16:33 ` ola.olsson at acconeer dot com
2020-04-17 6:59 ` rguenth at gcc dot gnu.org
2020-04-17 7:00 ` rguenth at gcc dot gnu.org [this message]
2020-04-17 7:24 ` cvs-commit at gcc dot gnu.org
2020-04-17 8:34 ` [Bug tree-optimization/94621] [9 " jakub at gcc dot gnu.org
2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org
2020-09-17 10:44 ` jakub 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-94621-4-X0YZ1p0QDs@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).