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 target/98100] ICE in expand_debug_locations, at cfgexpand.c:5610
Date: Tue, 20 Apr 2021 23:30:33 +0000 [thread overview]
Message-ID: <bug-98100-4-6Z1wmzJUMj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98100-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98100
--- 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:c47d4bddf3b08f833b2a59cc0be40234fe10e6bc
commit r9-9398-gc47d4bddf3b08f833b2a59cc0be40234fe10e6bc
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Dec 4 12:18:21 2020 +0100
debug: Fix another vector DECL_MODE ICE [PR98100]
The PR88587 fix changes DECL_MODE of vars with vector type during
inlining/cloning
when the vars are copied, so that their DECL_MODE matches their TYPE_MODE
in
the new function. Unfortunately, the following testcase still ICEs, the
var
isn't really used in the new function and so it isn't copied, but becomes
just a nonlocalized var. So we can't adjust its DECL_MODE because it
appears in multiple functions and needs different modes in between them.
The following patch changes the DEBUG_INSN creation to use TYPE_MODE
instead
of DECL_MODE for vars with vector types.
2020-12-04 Jakub Jelinek <jakub@redhat.com>
PR target/98100
* cfgexpand.c (expand_gimple_basic_block): For vars with
vector type, use TYPE_MODE rather than DECL_MODE.
* gcc.target/i386/pr98100.c: New test.
(cherry picked from commit 4c18faa4dd4dffdb76bc879b7555574ce3f4da01)
next prev parent reply other threads:[~2021-04-20 23:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 17:09 [Bug c/98100] New: " gscfq@t-online.de
2020-12-03 7:19 ` [Bug target/98100] " rguenth at gcc dot gnu.org
2020-12-03 8:06 ` marxin at gcc dot gnu.org
2020-12-03 13:19 ` jakub at gcc dot gnu.org
2020-12-03 13:23 ` jakub at gcc dot gnu.org
2020-12-03 13:34 ` jakub at gcc dot gnu.org
2020-12-04 11:18 ` cvs-commit at gcc dot gnu.org
2020-12-04 11:19 ` jakub at gcc dot gnu.org
2021-01-06 9:39 ` cvs-commit 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
2021-09-11 14:21 ` pinskia 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-98100-4-6Z1wmzJUMj@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).