[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a38QrxsWNZ2PNuWVGqg533Fcm9fYBbq2ehkbFvzfrwQ7g@mail.gmail.com>
Date: Tue, 7 Apr 2020 21:30:55 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
linux-xfs <linux-xfs@...r.kernel.org>
Subject: Re: libelf-0.175 breaks objtool
On Tue, Apr 7, 2020 at 8:44 PM Arnd Bergmann <arnd@...db.de> wrote:
> On Tue, Apr 7, 2020 at 6:33 PM Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> > On Tue, Apr 07, 2020 at 05:46:23PM +0200, Arnd Bergmann wrote:
> That is very possible. The -g has been there since xfs was originally merged
> back in 2002, and I could not figure out why it was there (unlike the
> -DSTATIC=""
> and -DDEBUG flags that are set in the same line).
>
> On the other hand, my feeling is that setting -g should not cause problems
> with objtool, if CONFIG_DEBUG_INFO is ok.
Nevermind, I now see the same problem in lots of files in a configuration
setting these options:
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_INFO_REDUCED=y
# CONFIG_DEBUG_INFO_SPLIT is not set
CONFIG_DEBUG_INFO_DWARF4=y
CONFIG_DEBUG_INFO_BTF=y
Not sure which of these are actually relevant, but I had other configurations
setting DEBUG_INFO that are not affected.
Arnd
Powered by blists - more mailing lists