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/96260] [10/11 Regression] RISC-V: -fsanitize=kernel-address is not available after gcc10 Date: Thu, 23 Jul 2020 07:19:57 +0000 [thread overview] Message-ID: <bug-96260-4-ROgb27wHxh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96260-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kito Cheng <kito@gcc.gnu.org>: https://gcc.gnu.org/g:2ca1b6d009b194286c3ec91f9c51cc6b0a475458 commit r11-2283-g2ca1b6d009b194286c3ec91f9c51cc6b0a475458 Author: Kito Cheng <kito.cheng@sifive.com> Date: Wed Jul 22 14:50:40 2020 +0800 PR target/96260 - KASAN should work even back-end not porting anything. - Most KASAN function don't need any porting anything in back-end except asan stack protection. - However kernel will given shadow offset when enable asan stack protection, so eveything in KASAN can work if shadow offset is given. - Verified with x86 and risc-v. - Verified with RISC-V linux kernel. gcc/ChangeLog: PR target/96260 * asan.c (asan_shadow_offset_set_p): New. * asan.h (asan_shadow_offset_set_p): Ditto. * toplev.c (process_options): Allow -fsanitize=kernel-address even TARGET_ASAN_SHADOW_OFFSET not implemented, only check when asan stack protection is enabled. gcc/testsuite/ChangeLog: PR target/96260 * gcc.target/riscv/pr91441.c: Update warning message. * gcc.target/riscv/pr96260.c: New.
next prev parent reply other threads:[~2020-07-23 7:19 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-21 10:14 [Bug target/96260] New: " green.hu at gmail dot com 2020-07-21 10:38 ` [Bug target/96260] " schwab@linux-m68k.org 2020-07-21 11:25 ` kito at gcc dot gnu.org 2020-07-21 14:22 ` [Bug target/96260] [10/11 Regression] " rguenth at gcc dot gnu.org 2020-07-23 6:52 ` rguenth at gcc dot gnu.org 2020-07-23 7:19 ` cvs-commit at gcc dot gnu.org [this message] 2020-07-23 7:48 ` cvs-commit at gcc dot gnu.org 2020-07-23 7:49 ` kito 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-96260-4-ROgb27wHxh@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).