[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+ASDXOOyd4-thctnHG06GXnouf6EuJ4QV5QM+3iNBYQF499uA@mail.gmail.com>
Date: Fri, 12 Jul 2019 18:46:31 -0700
From: Brian Norris <briannorris@...omium.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Jason Baron <jbaron@...mai.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Kees Cook <keescook@...omium.org>,
Borislav Petkov <bp@...e.de>,
Michal Marek <michal.lkml@...kovi.net>
Subject: Re: [RFC PATCH] bug: always show source-tree-relative paths in WARN()/BUG()
On Thu, Jul 11, 2019 at 6:50 PM Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
> GCC 8 added this flag.
> So, it will be eventually all solved in the GCC world.
Ack.
> Clang has not supported it yet...
That's what it appeared like. I've bugged our Clang-loving toolchain
folks to see if we can get parity.
> Trimming absolute path at run-time
> is no help for reducing the kernel image.
Sure, but that's not my stated goal. It would indeed be nicer though.
I guess if no one else speaks up with a favorable word toward my RFC,
I'll just see what I can do on the toolchain side.
Thanks for the help,
Brian
Powered by blists - more mailing lists