From: Nick Desaulniers <ndesaulniers@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Miroslav Benes <mbenes@suse.cz>,
linux-toolchains <linux-toolchains@vger.kernel.org>
Subject: Re: [PATCH v2 9/9] objtool: Ignore exc_double_fault() __noreturn warnings
Date: Fri, 14 Apr 2023 14:16:50 -0700 [thread overview]
Message-ID: <CAKwvOdn9r96UznjbghdceDXyZxsrsvwj99Noxw=u3Ak_kBvacQ@mail.gmail.com> (raw)
In-Reply-To: <20230413092409.GJ4253@hirez.programming.kicks-ass.net>
On Thu, Apr 13, 2023 at 2:24 AM Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Wed, Apr 12, 2023 at 12:03:24PM -0700, Josh Poimboeuf wrote:
> > + * - have compiler communicate __noreturn functions somehow
Could probably stuff these in some kind of "noreturn function symbol
table"/custom elf section; DWARF tags are nice but we don't always
want debug info. (I should ask colleagues if there's anything like
this in DWARF already, perhaps for DWARFv6).
>
> This, we're going to have to do that -- because keeping that (ever
> growing) list in sync is going to be a pain in the backside.
>
--
Thanks,
~Nick Desaulniers
parent reply other threads:[~2023-04-14 21:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230413092409.GJ4253@hirez.programming.kicks-ass.net>]
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='CAKwvOdn9r96UznjbghdceDXyZxsrsvwj99Noxw=u3Ak_kBvacQ@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).