public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: libelf-0.175 breaks objtool
Date: Thu, 9 Apr 2020 00:41:30 -0700	[thread overview]
Message-ID: <20200409074130.GD21033@infradead.org> (raw)
In-Reply-To: <CAK8P3a3piAV7BbgH-y_zqj4XmLcBQqKZ-NHPcqo4OTF=4H3UFA@mail.gmail.com>

On Tue, Apr 07, 2020 at 08:44:11PM +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.

I suspect we shouldn't force -g ourselves in xfs.  Care to send a patch?

  parent reply	other threads:[~2020-04-09  7:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 18:38 libelf-0.175 breaks objtool Steven Rostedt
2019-02-06  2:16 ` Josh Poimboeuf
2019-02-06 17:16   ` Steven Rostedt
2020-04-06 21:07     ` Arnd Bergmann
2020-04-06 22:16       ` Josh Poimboeuf
2020-04-06 22:31         ` Arnd Bergmann
2020-04-07 15:46           ` Arnd Bergmann
2020-04-07 16:32             ` Josh Poimboeuf
2020-04-07 18:44               ` Arnd Bergmann
2020-04-07 19:30                 ` Arnd Bergmann
2020-04-09  7:41                 ` Christoph Hellwig [this message]
2020-04-09  8:25                   ` Arnd Bergmann
2020-04-10  0:46                     ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200409074130.GD21033@infradead.org \
    --to=hch@infradead.org \
    --cc=arnd@arndb.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox