From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ilie Halip <ilie.halip@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: objtool warning "uses BP as a scratch register" with clang-9
Date: Tue, 27 Aug 2019 14:22:55 -0500 [thread overview]
Message-ID: <20190827192255.wbyn732llzckmqmq@treble> (raw)
In-Reply-To: <CAK8P3a2TeaMc_tWzzjuqO-eQjZwJdpbR1yH8yzSQbbVKdWCwSg@mail.gmail.com>
On Tue, Aug 27, 2019 at 09:00:52PM +0200, Arnd Bergmann wrote:
> On Tue, Aug 27, 2019 at 5:00 PM Ilie Halip <ilie.halip@gmail.com> wrote:
> >
> > > > $ clang-9 -c crc32.i -O2 ; objtool check crc32.o
> > > > crc32.o: warning: objtool: fn1 uses BP as a scratch register
> >
> > Yes, I see it too. https://godbolt.org/z/N56HW1
> >
> > > Do you still see this warning with -fno-omit-frame-pointer (assuming
> > > clang has that option)?
> >
> > Using this makes the warning go away. Running objtool with --no-fp
> > also gets rid of it.
>
> I still see the warning after adding back the -fno-omit-frame-pointer
> in my reduced test case:
>
> $ clang-9 -c crc32.i -Werror -Wno-address-of-packed-member -Wall
> -Wno-pointer-sign -Wno-unused-value -Wno-constant-logical-operand -O2
> -Wno-unused -fno-omit-frame-pointer
> $ objtool check crc32.o
> crc32.o: warning: objtool: fn1 uses BP as a scratch register
This warning most likely means that clang is clobbering RBP in leaf
functions. With -fno-omit-frame-pointer, leaf functions don't need to
set up the frame pointer, but they at least need to leave RBP untouched,
so that an interrupts/exceptions can unwind through the function.
--
Josh
next prev parent reply other threads:[~2019-08-27 19:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 12:30 Arnd Bergmann
2019-08-27 14:51 ` Josh Poimboeuf
2019-08-27 14:59 ` Ilie Halip
2019-08-27 19:00 ` Arnd Bergmann
2019-08-27 19:22 ` Josh Poimboeuf [this message]
2019-08-27 19:47 ` Arnd Bergmann
2019-08-27 21:21 ` Nick Desaulniers
2019-08-28 9:00 ` Arnd Bergmann
2019-08-28 14:06 ` Arnd Bergmann
2019-08-28 14:51 ` Josh Poimboeuf
2019-08-28 15:29 ` Arnd Bergmann
2019-08-28 17:57 ` Josh Poimboeuf
2019-08-28 19:41 ` Arnd Bergmann
2019-08-28 15:13 ` Arnd Bergmann
2019-08-28 15:22 ` Josh Poimboeuf
2019-08-28 15:28 ` Arnd Bergmann
2019-08-28 15:40 ` Arnd Bergmann
2019-08-29 23:24 ` Josh Poimboeuf
2019-08-30 10:44 ` Arnd Bergmann
2019-08-30 15:14 ` Josh Poimboeuf
2019-08-30 15:58 ` Arnd Bergmann
2019-08-30 16:12 ` David Laight
2019-08-30 16:03 ` Linus Torvalds
2019-08-29 17:34 ` Josh Poimboeuf
2019-08-29 18:30 ` Linus Torvalds
2019-08-29 20:21 ` Arnd Bergmann
2019-08-29 22:26 ` Linus Torvalds
2019-08-30 15:02 ` Josh Poimboeuf
2019-08-30 15:39 ` David Laight
2019-08-30 15:48 ` Linus Torvalds
2019-08-30 15:55 ` David Laight
2019-08-30 16:01 ` Linus Torvalds
2019-08-30 16:42 ` David Laight
2019-08-30 16:49 ` Josh Poimboeuf
2019-09-02 9:02 ` David Laight
2019-09-04 11:53 ` Geert Uytterhoeven
2019-08-28 22:13 ` Nick Desaulniers
2019-08-29 0:28 ` Josh Poimboeuf
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=20190827192255.wbyn732llzckmqmq@treble \
--to=jpoimboe@redhat.com \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=ilie.halip@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
/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
all inboxes | Powered by JetHome®