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/99324] [8/9 Regression] ICE in mark_addressable, at gimple-expr.c:918 since r6-314
Date: Tue, 20 Apr 2021 23:33:09 +0000 [thread overview]
Message-ID: <bug-99324-4-D5VmRKAMQ4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99324-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99324
--- 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:12cd8e1b690a22c478f91671dd7cf5f6cf8332a7
commit r9-9428-g12cd8e1b690a22c478f91671dd7cf5f6cf8332a7
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Mar 3 09:55:19 2021 +0100
c-family: Avoid ICE on va_arg [PR99324]
build_va_arg calls the middle-end mark_addressable, which e.g. requires
that
cfun is non-NULL. The following patch calls instead
c_common_mark_addressable_vec
which is the c-family variant similarly to the FE c_mark_addressable and
cxx_mark_addressable, except that it doesn't error on addresses of register
variables. As the taking of the address is artificial for the .VA_ARG
ifn and when that is lowered goes away, it is similar case to the vector
subscripting for which c_common_mark_addressable_vec has been added.
2021-03-03 Jakub Jelinek <jakub@redhat.com>
PR c/99324
* c-common.c (build_va_arg): Call c_common_mark_addressable_vec
instead of mark_addressable. Fix a comment typo -
neutrallly -> neutrally.
* gcc.c-torture/compile/pr99324.c: New test.
(cherry picked from commit 0e87dc86eb56f732a41af2590f0b807031003fbe)
next prev parent reply other threads:[~2021-04-20 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 17:05 [Bug c/99324] New: ICE in mark_addressable, at gimple-expr.c:918 gscfq@t-online.de
2021-03-02 7:42 ` [Bug c/99324] " rguenth at gcc dot gnu.org
2021-03-02 9:45 ` [Bug c/99324] [8/9/10/11 Regression] ICE in mark_addressable, at gimple-expr.c:918 since r6-314 jakub at gcc dot gnu.org
2021-03-02 10:02 ` jakub at gcc dot gnu.org
2021-03-02 10:27 ` rguenth at gcc dot gnu.org
2021-03-02 11:30 ` jakub at gcc dot gnu.org
2021-03-03 8:55 ` cvs-commit at gcc dot gnu.org
2021-03-03 8:58 ` [Bug c/99324] [8/9/10 " jakub at gcc dot gnu.org
2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org
2021-03-20 8:09 ` [Bug c/99324] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-22 16:51 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` 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-99324-4-D5VmRKAMQ4@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).