public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/96307] New: ICE in sanopt on riscv64 since r11-2283-g2ca1b6d009b194286c3ec91f9c51cc6b0a475458
Date: Fri, 24 Jul 2020 09:44:47 +0000 [thread overview]
Message-ID: <bug-96307-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96307
Bug ID: 96307
Summary: ICE in sanopt on riscv64 since
r11-2283-g2ca1b6d009b194286c3ec91f9c51cc6b0a475458
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, kito at gcc dot gnu.org,
marxin at gcc dot gnu.org
Target Milestone: ---
I see the following ICE with a cross compiler:
$ riscv64-linux-gnu-gcc
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/lto/c-compatible-types-1_1.c
-fsanitize=kernel-address --param=asan-instrumentation-with-call-threshold=8
during GIMPLE pass: sanopt
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/lto/c-compatible-types-1_1.c:
In function ‘t’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/lto/c-compatible-types-1_1.c:9:1:
internal compiler error: Segmentation fault
9 | t()
| ^
0xae236f crash_signal
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/toplev.c:328
0x7ffff78d752f ???
/usr/src/debug/glibc-2.31-6.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2020-07-24 9:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 9:44 marxin at gcc dot gnu.org [this message]
2020-07-24 9:57 ` [Bug sanitizer/96307] " kito at gcc dot gnu.org
2020-07-24 10:16 ` [Bug sanitizer/96307] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-08-05 3:52 ` wilson at gcc dot gnu.org
2020-09-21 10:38 ` marxin at gcc dot gnu.org
2020-09-21 15:33 ` kito at gcc dot gnu.org
2020-10-12 12:43 ` rguenth at gcc dot gnu.org
2020-10-16 6:13 ` kito at gcc dot gnu.org
2020-11-06 3:23 ` cvs-commit at gcc dot gnu.org
2020-11-06 3:35 ` kito at gcc dot gnu.org
2021-01-14 9:05 ` rguenth at gcc dot gnu.org
2021-02-01 9:43 ` [Bug sanitizer/96307] [10 " cvs-commit at gcc dot gnu.org
2021-02-02 8:58 ` kito at gcc dot gnu.org
2021-03-12 14:05 ` schwab@linux-m68k.org
2021-03-12 17:26 ` schwab@linux-m68k.org
2021-03-16 10:37 ` kito at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-07-07 8:58 ` rguenth 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-96307-4@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).