public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10
@ 2020-07-21 10:14 green.hu at gmail dot com
2020-07-21 10:38 ` [Bug target/96260] " schwab@linux-m68k.org
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: green.hu at gmail dot com @ 2020-07-21 10:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260
Bug ID: 96260
Summary: RISC-V: -fsanitize=kernel-address is not available
after gcc10
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: green.hu at gmail dot com
Target Milestone: ---
Target: riscv64
It used to work to build riscv64 Linux kernel with this option
"-fsanitize=kernel-address" for KASAN in gcc9 however it doesn't work in gcc10.
cc1: warning: '-fsanitize=address' and '-fsanitize=kernel-address' are not
supported for this target
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/96260] RISC-V: -fsanitize=kernel-address is not available after gcc10
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 green.hu at gmail dot com
@ 2020-07-21 10:38 ` schwab@linux-m68k.org
2020-07-21 11:25 ` kito at gcc dot gnu.org
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: schwab@linux-m68k.org @ 2020-07-21 10:38 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260
Andreas Schwab <schwab@linux-m68k.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |91441
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
See PR91441.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91441
[Bug 91441] ICE in asan_shadow_offset at asan.c:342 on riscv64 target
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/96260] RISC-V: -fsanitize=kernel-address is not available after gcc10
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 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
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: kito at gcc dot gnu.org @ 2020-07-21 11:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260
Kito Cheng <kito at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kito at gcc dot gnu.org
--- Comment #2 from Kito Cheng <kito at gcc dot gnu.org> ---
Yeah, seems like I fix PR91441 in wrong way.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/96260] [10/11 Regression] RISC-V: -fsanitize=kernel-address is not available after gcc10
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 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 ` rguenth at gcc dot gnu.org
2020-07-23 6:52 ` rguenth at gcc dot gnu.org
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: rguenth at gcc dot gnu.org @ 2020-07-21 14:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.2
Summary|RISC-V: |[10/11 Regression] RISC-V:
|-fsanitize=kernel-address |-fsanitize=kernel-address
|is not available after |is not available after
|gcc10 |gcc10
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/96260] [10/11 Regression] RISC-V: -fsanitize=kernel-address is not available after gcc10
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 green.hu at gmail dot com
` (2 preceding siblings ...)
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
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: rguenth at gcc dot gnu.org @ 2020-07-23 6:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.2 |10.3
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 10.2 is released, adjusting target milestone.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/96260] [10/11 Regression] RISC-V: -fsanitize=kernel-address is not available after gcc10
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 green.hu at gmail dot com
` (3 preceding siblings ...)
2020-07-23 6:52 ` rguenth at gcc dot gnu.org
@ 2020-07-23 7:19 ` cvs-commit at gcc dot gnu.org
2020-07-23 7:48 ` cvs-commit at gcc dot gnu.org
2020-07-23 7:49 ` kito at gcc dot gnu.org
6 siblings, 0 replies; 8+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-07-23 7:19 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/96260] [10/11 Regression] RISC-V: -fsanitize=kernel-address is not available after gcc10
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 green.hu at gmail dot com
` (4 preceding siblings ...)
2020-07-23 7:19 ` cvs-commit at gcc dot gnu.org
@ 2020-07-23 7:48 ` cvs-commit at gcc dot gnu.org
2020-07-23 7:49 ` kito at gcc dot gnu.org
6 siblings, 0 replies; 8+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-07-23 7:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Kito Cheng <kito@gcc.gnu.org>:
https://gcc.gnu.org/g:83f1fbb9e7afaa77d52b200c7937788faa5f24d7
commit r10-8516-g83f1fbb9e7afaa77d52b200c7937788faa5f24d7
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.
(cherry picked from commit 2ca1b6d009b194286c3ec91f9c51cc6b0a475458)
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/96260] [10/11 Regression] RISC-V: -fsanitize=kernel-address is not available after gcc10
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 green.hu at gmail dot com
` (5 preceding siblings ...)
2020-07-23 7:48 ` cvs-commit at gcc dot gnu.org
@ 2020-07-23 7:49 ` kito at gcc dot gnu.org
6 siblings, 0 replies; 8+ messages in thread
From: kito at gcc dot gnu.org @ 2020-07-23 7:49 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96260
Kito Cheng <kito at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Kito Cheng <kito at gcc dot gnu.org> ---
Fixed on GCC 10 branch and trunk.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2020-07-23 7:49 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-21 10:14 [Bug target/96260] New: RISC-V: -fsanitize=kernel-address is not available after gcc10 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
2020-07-23 7:48 ` cvs-commit at gcc dot gnu.org
2020-07-23 7:49 ` kito at gcc dot gnu.org
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).