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 c++/98353] [8/9 Regression] ICE in propagate_necessity, at tree-ssa-dce.c:1053 since r6-4886-gcda0a029f45d20f4
Date: Tue, 20 Apr 2021 23:30:59 +0000 [thread overview]
Message-ID: <bug-98353-4-7vRqhTLJJ9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98353-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98353
--- Comment #9 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:202240b05f28681053c64efbf1e6deb07f36e1b8
commit r9-9403-g202240b05f28681053c64efbf1e6deb07f36e1b8
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Dec 22 00:01:34 2020 +0100
gimplify: Gimplify value in gimplify_init_ctor_eval_range [PR98353]
gimplify_init_ctor_eval_range wasn't gimplifying value, so if it wasn't
a gimple val, verification at the end of gimplification would ICE (or with
release checking some random pass later on would ICE or misbehave).
2020-12-21 Jakub Jelinek <jakub@redhat.com>
PR c++/98353
* gimplify.c (gimplify_init_ctor_eval_range): Gimplify value before
storing it into cref.
* g++.dg/opt/pr98353.C: New test.
(cherry picked from commit f3113a85f098df8165624321cc85d20219fb2ada)
next prev parent reply other threads:[~2021-04-20 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 16:47 [Bug c++/98353] New: [9/10/11 Regression] ICE in propagate_necessity, at tree-ssa-dce.c:1053 gscfq@t-online.de
2020-12-18 8:44 ` [Bug c++/98353] [9/10/11 Regression] ICE in propagate_necessity, at tree-ssa-dce.c:1053 since r6-4886-gcda0a029f45d20f4 marxin at gcc dot gnu.org
2020-12-21 12:17 ` jakub at gcc dot gnu.org
2020-12-21 12:47 ` [Bug c++/98353] [8/9/10/11 " jakub at gcc dot gnu.org
2020-12-21 12:53 ` jakub at gcc dot gnu.org
2020-12-21 23:03 ` cvs-commit at gcc dot gnu.org
2020-12-21 23:33 ` [Bug c++/98353] [8/9/10 " jakub at gcc dot gnu.org
2020-12-23 21:48 ` cvs-commit at gcc dot gnu.org
2021-01-05 8:32 ` rguenth at gcc dot gnu.org
2021-01-06 9:40 ` cvs-commit at gcc dot gnu.org
2021-01-06 9:46 ` [Bug c++/98353] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:30 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-22 16:49 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:08 ` 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-98353-4-7vRqhTLJJ9@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).