[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200219140927.396ca577@gandalf.local.home>
Date: Wed, 19 Feb 2020 14:09:27 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Nathan Chancellor <natechancellor@...il.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Arnd Bergmann <arnd@...db.de>, Ingo Molnar <mingo@...hat.com>,
Jason Baron <jbaron@...mai.com>,
Catalin Marinas <catalin.marinas@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
clang-built-linux <clang-built-linux@...glegroups.com>
Subject: Re: [PATCH 3/6] tracing: Wrap section comparison in
tracer_alloc_buffers with COMPARE_SECTIONS
On Wed, 19 Feb 2020 14:16:19 -0400
Jason Gunthorpe <jgg@...pe.ca> wrote:
> > kernel/trace/trace.h
> > 1923:extern const char *__stop___trace_bprintk_fmt[];
>
> Godbolt says clang is happy if it is written as:
>
> if (&__stop___trace_bprintk_fmt[0] != &__start___trace_bprintk_fmt[0])
>
> Which is probably the best compromise. The type here is const char
> *[], so it would be a shame to see it go.
If the above works, I'd be happy with that. As it is still readable.
-- Steve
Powered by blists - more mailing lists