public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94621] [9 Regression] GCC 9.2.1 segfaults when compiling file with -O3 since r9-5354
Date: Wed, 16 Sep 2020 19:20:33 +0000 [thread overview]
Message-ID: <bug-94621-4-2rGMn47JHI@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 #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:5b23b0c44692cc5e4d5e726f96497bff73094e7b
commit r9-8880-g5b23b0c44692cc5e4d5e726f96497bff73094e7b
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Apr 17 09:07:49 2020 +0200
inliner: Don't ICE on NULL TYPE_DOMAIN [PR94621]
When I've added the VLA tweak for OpenMP to avoid error_mark_nodes in the
IL in
type, I forgot that TYPE_DOMAIN could be NULL. Furthermore, as an
optimization,
this patch checks the hopefully cheapest condition that is very likely
false
most of the time (enabled only during OpenMP handling) first.
2020-04-17 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/94621
* tree-inline.c (remap_type_1): Don't dereference NULL TYPE_DOMAIN.
Move id->adjust_array_error_bounds check first in the condition.
* gcc.c-torture/compile/pr94621.c: New test.
(cherry picked from commit c58cb6ac6891886b7aa01c440ac71a5e7cbcba97)
next prev parent reply other threads:[~2020-09-16 19:20 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
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 [this message]
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-2rGMn47JHI@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).