[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNMpnY54kDdGwOPOD84UDf=Fzqtu62ifTds2vZn4t4YigQ@mail.gmail.com>
Date: Tue, 19 Nov 2019 17:12:16 +0100
From: Marco Elver <elver@...gle.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
kasan-dev <kasan-dev@...glegroups.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
"Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: linux-next: Tree for Nov 19 (kcsan)
On Tue, 19 Nov 2019 at 16:11, Randy Dunlap <rdunlap@...radead.org> wrote:
>
> On 11/19/19 12:46 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20191118:
> >
>
> on x86_64:
>
> It seems that this function can already be known by the compiler as a
> builtin:
>
> ../kernel/kcsan/core.c:619:6: warning: conflicting types for built-in function ‘__tsan_func_exit’ [-Wbuiltin-declaration-mismatch]
> void __tsan_func_exit(void)
> ^~~~~~~~~~~~~~~~
>
>
> $ gcc --version
> gcc (SUSE Linux) 7.4.1 20190905 [gcc-7-branch revision 275407]
Interesting. Could you share the .config? So far I haven't been able
to reproduce.
I can get the warning if I manually add -fsanitize=thread to flags for
kcsan/core.c (but normally disabled via KCSAN_SANITIZE := n). If
possible could you also share the output of `make V=1` for
kcsan/core.c?
Thanks,
-- Marco
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@...radead.org>
Powered by blists - more mailing lists