From: Arnd Bergmann <arnd@arndb.de>
To: clang-built-linux <clang-built-linux@googlegroups.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: warning: objtool: fn1 uses BP as a scratch register
Date: Fri, 19 Jul 2019 20:09:47 +0200 [thread overview]
Message-ID: <CAK8P3a12cVdrEXdgWkHGHP6O04mz5khaB7WgQ1nvOptaUTu_SA@mail.gmail.com> (raw)
A lot of objtool fixes showed up in linux-next, so I looked at some
remaining ones.
This one comes a lot up in some configurations
https://godbolt.org/z/ZZLVD-
struct ov7670_win_size {
int width;
int height;
};
struct ov7670_devtype {
struct ov7670_win_size *win_sizes;
unsigned n_win_sizes;
};
struct ov7670_info {
int min_width;
int min_height;
struct ov7670_devtype devtype;
} a;
int b;
int fn1() {
struct ov7670_info c = a;
int i = 0;
for (; i < c.devtype.n_win_sizes; i++) {
struct ov7670_win_size d = c.devtype.win_sizes[i];
if (c.min_width && d.width < d.height < c.min_height)
if (b)
return 0;
}
return 2;
}
$ clang-8 -O2 -fno-omit-frame-pointer -fno-strict-overflow -c ov7670.i
$ objtool check --no-unreachable --uaccess ov7670.o
ov7670.o: warning: objtool: fn1 uses BP as a scratch register
Arnd
next reply other threads:[~2019-07-19 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 18:09 Arnd Bergmann [this message]
2019-07-19 18:23 ` warning: objtool: fn1 uses BP as a scratch register Nick Desaulniers
2019-07-19 18:31 ` Josh Poimboeuf
2019-07-19 18:44 ` Arnd Bergmann
2019-07-19 18:48 ` Nick Desaulniers
2019-07-19 18:50 ` Nick Desaulniers
2019-07-19 19:43 ` Arnd Bergmann
2019-07-22 19:46 ` Topper, Craig
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=CAK8P3a12cVdrEXdgWkHGHP6O04mz5khaB7WgQ1nvOptaUTu_SA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).