public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/98601] [8/9/10/11 Regression] aarch64: ICE in rtx_addr_can_trap_p_1, at rtlanal.c:467
Date: Wed, 31 Mar 2021 10:30:18 +0000 [thread overview]
Message-ID: <bug-98601-4-be9tW2D0Gr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98601-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98601
Alex Coplan <acoplan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|aarch64: ICE in |[8/9/10/11 Regression]
|rtx_addr_can_trap_p_1, at |aarch64: ICE in
|rtlanal.c:467 |rtx_addr_can_trap_p_1, at
| |rtlanal.c:467
Target|aarch64 |arm aarch64
--- Comment #1 from Alex Coplan <acoplan at gcc dot gnu.org> ---
ICEs started with GCC 8. GCC 7 accepts the code with a warning (warning:
dereferencing 'void *' pointer).
Clearly we should fix the ICE, but I'm wondering whether this code is actually
valid?
clang rejects it with "error: dereference of pointer to incomplete type 'void'"
x86-64 GCC rejects it with:
<source>:3:3: error: invalid use of void expression
3 | asm("" : "=Q"(*b));
| ^~~
<source>:3:3: error: invalid lvalue in 'asm' output 0
We also hit the same ICE with this testcase on AArch32, FWIW.
next prev parent reply other threads:[~2021-03-31 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 13:08 [Bug rtl-optimization/98601] New: " acoplan at gcc dot gnu.org
2021-03-31 10:30 ` acoplan at gcc dot gnu.org [this message]
2021-03-31 11:00 ` [Bug rtl-optimization/98601] [8/9/10/11 Regression] " acoplan at gcc dot gnu.org
2021-03-31 11:41 ` [Bug target/98601] " rguenth at gcc dot gnu.org
2021-03-31 11:50 ` [Bug rtl-optimization/98601] " rguenth at gcc dot gnu.org
2021-03-31 12:51 ` acoplan at gcc dot gnu.org
2021-04-09 8:05 ` rguenth at gcc dot gnu.org
2021-04-09 9:16 ` jakub at gcc dot gnu.org
2021-04-09 9:28 ` jakub at gcc dot gnu.org
2021-04-10 10:47 ` cvs-commit at gcc dot gnu.org
2021-04-10 10:50 ` [Bug rtl-optimization/98601] [8/9/10 " jakub at gcc dot gnu.org
2021-04-20 9:45 ` cvs-commit at gcc dot gnu.org
2021-04-20 9:52 ` [Bug rtl-optimization/98601] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:52 ` 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-98601-4-be9tW2D0Gr@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).