public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/96307] [10/11 Regression] ICE in sanopt on riscv64 since r11-2283-g2ca1b6d009b194286c3ec91f9c51cc6b0a475458 Date: Wed, 05 Aug 2020 03:52:46 +0000 [thread overview] Message-ID: <bug-96307-4-7dfVlGBCum@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96307-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96307 Jim Wilson <wilson at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wilson at gcc dot gnu.org --- Comment #2 from Jim Wilson <wilson at gcc dot gnu.org> --- It is calling targetm.asan_shadow_offset which is a null function pointer currently for RISC-V. This is related to Kito's recent patch to re-enable ksan support when asan_shadow_offset isn't defined. But it looks like there are multiple params that can cause asan_shadow_offset to be called for ksan when it normally isn't. So this change may need to be removed. Good news is that we have a patch to add asan support for RISC-V which would make Kito's toplev.c patch unnecessary for us.
next prev parent reply other threads:[~2020-08-05 3:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-24 9:44 [Bug sanitizer/96307] New: " marxin at gcc dot gnu.org 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 [this message] 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-7dfVlGBCum@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: linkBe 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).