From: Josh Poimboeuf <jpoimboe@redhat.com>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Greg KH <gregkh@linuxfoundation.org>,
David Laight <David.Laight@ACULAB.COM>,
damian <damian.tometzki@icloud.com>
Subject: [PATCH 0/3] objtool: GCC 8 support
Date: Wed, 9 May 2018 22:39:13 -0500 [thread overview]
Message-ID: <cover.1525923412.git.jpoimboe@redhat.com> (raw)
Now that GCC 8 is out, several people have complained about a bunch of
objtool warnings. These patches fix all known warnings.
Patch 1 is a repost of a previous fix -- unrelated to GCC 8, but a
prereq for the following two patches.
Patch 2 fixes the vast majority of the warnings, caused by GCC 8's new
usage of "cold" subfunctions for unlikely text.
Patch 3 fixes a few more warnings, related to switch tables.
Josh Poimboeuf (3):
objtool: Fix "noreturn" detection for recursive sibling calls
objtool: Support GCC 8 cold subfunctions
objtool: Support GCC 8 switch tables
tools/objtool/check.c | 125 ++++++++++++++++++++++++++----------------
tools/objtool/elf.c | 42 +++++++++++++-
tools/objtool/elf.h | 2 +
3 files changed, 121 insertions(+), 48 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-10 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 3:39 Josh Poimboeuf [this message]
2018-05-10 3:39 ` [PATCH 1/3] objtool: Fix "noreturn" detection for recursive sibling calls Josh Poimboeuf
2018-05-14 12:37 ` [tip:core/urgent] " tip-bot for Josh Poimboeuf
2018-05-10 3:39 ` [PATCH 2/3] objtool: Support GCC 8 cold subfunctions Josh Poimboeuf
2018-05-14 12:37 ` [tip:core/urgent] objtool: Support GCC 8's " tip-bot for Josh Poimboeuf
2018-05-10 3:39 ` [PATCH 3/3] objtool: Support GCC 8 switch tables Josh Poimboeuf
2018-05-10 8:41 ` Peter Zijlstra
2018-05-10 12:44 ` [PATCH v1.1 " Josh Poimboeuf
2018-05-10 14:07 ` Peter Zijlstra
2018-05-10 22:45 ` [PATCH v1.2 " Josh Poimboeuf
2018-05-10 22:48 ` [PATCH v1.3 " Josh Poimboeuf
2018-05-14 12:38 ` [tip:core/urgent] " tip-bot for 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=cover.1525923412.git.jpoimboe@redhat.com \
--to=jpoimboe@redhat.com \
--cc=David.Laight@ACULAB.COM \
--cc=arnd@arndb.de \
--cc=damian.tometzki@icloud.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.