On Tue, Jun 23, 2020 at 08:17PM +1000, Stephen Rothwell wrote: > Hi Peter, > > On Tue, 23 Jun 2020 11:32:30 +0200 Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > > > I suppose the next quest is finding a s390 compiler version that works > > and then bumping the version test in the aforementioned commit. > > Not a lot of help, but my Debian cross compiler seems to work: > > $ s390x-linux-gnu-gcc --version > s390x-linux-gnu-gcc (Debian 9.3.0-13) 9.3.0 Rummaging through changelogs led me to 8.3.0 as the first good GCC. Also confirmed by building that version and compiling a file that breaks with older versions. It seems the first major version to fix it was 9, but backported to 8.3. This is for all architectures. Suggested patch below. Thanks, -- Marco ------ >8 ------ From: Marco Elver <elver@xxxxxxxxxx> Date: Tue, 23 Jun 2020 12:57:42 +0200 Subject: [PATCH] kasan: Fix required compiler version The first working GCC version to satisfy CC_HAS_WORKING_NOSANITIZE_ADDRESS is GCC 8.3.0. Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89124 Reported-by: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> Signed-off-by: Marco Elver <elver@xxxxxxxxxx> --- lib/Kconfig.kasan | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan index 7a496b885f46..19fba15e99c6 100644 --- a/lib/Kconfig.kasan +++ b/lib/Kconfig.kasan @@ -16,7 +16,7 @@ config CC_HAS_KASAN_SW_TAGS def_bool $(cc-option, -fsanitize=kernel-hwaddress) config CC_HAS_WORKING_NOSANITIZE_ADDRESS - def_bool !CC_IS_GCC || GCC_VERSION >= 80000 + def_bool !CC_IS_GCC || GCC_VERSION >= 80300 config KASAN bool "KASAN: runtime memory debugger" -- 2.27.0.111.gc72c7da667-goog
