From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Add attributes for setjmp/longjmp
Date: Thu, 19 Sep 2019 20:25:50 +1000 (AEST) [thread overview]
Message-ID: <46YtKW0Z7hz9sN1@ozlabs.org> (raw)
In-Reply-To: <c02ce4a573f3bac907e2c70957a2d1275f910013.1567605586.git.segher@kernel.crashing.org>
On Wed, 2019-09-04 at 14:11:07 UTC, Segher Boessenkool wrote:
> The setjmp function should be declared as "returns_twice", or bad
> things can happen[1]. This does not actually change generated code
> in my testing.
>
> The longjmp function should be declared as "noreturn", so that the
> compiler can optimise calls to it better. This makes the generated
> code a little shorter.
>
> Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/aa497d4352414aad22e792b35d0aaaa12bbc37c5
cheers
prev parent reply other threads:[~2019-09-19 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 14:11 [PATCH] powerpc: Add attributes for setjmp/longjmp Segher Boessenkool
2019-09-19 10:25 ` Michael Ellerman [this message]
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=46YtKW0Z7hz9sN1@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).