From: Jeff Johnston <jjohnstn@redhat.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: newlib@sourceware.org
Subject: Re: [PATCH] sparc: Improve setjmp()
Date: Thu, 12 Oct 2023 11:33:32 -0400 [thread overview]
Message-ID: <CAOox84v8AvKsZqdW3wAn1GNvLw2oUY29ww0CqXLXXOF_4htfBQ@mail.gmail.com> (raw)
In-Reply-To: <b9628180-2ee7-4866-98ca-a50be92e17a2@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 3810 bytes --]
On Thu, Oct 12, 2023 at 10:55 AM Sebastian Huber <
sebastian.huber@embedded-brains.de> wrote:
> Hello Jeff,
>
> On 12.10.23 16:50, Jeff Johnston wrote:
> > Hi Sebastian,
> >
> > I am not familiar with sparc to comment, but Corinna has performed
> > maintenance on the setjmp.S file if
> > you want to wait for her to look at the change. Otherwise, if you have
> > a test case that
> > verifies the change, feel free to merge and you can confirm with Corinna
> > when she is back.
>
> the glibc version does also the window flush. I noticed the issue by
> testing compiler builtins which on some systems result in a trap, for
> example:
>
Then by all means go ahead and check it in.
-- Jeff J.
>
> volatile int64_t n;
> volatile int64_t d;
>
> n = INT64_C( 0 );
> d = INT64_C( 0 );
> do_longjmp = true;
>
> if ( setjmp( exception_return_context ) == 0 ) {
> n = n % d;
> }
>
> In RTEMS, we use a processor-specific stack to handle synchronous
> exceptions. If you want to jump back to the thread from the exception
> handler, then you have to change back to the original thread stack. This
> works only if you flush the windows in the setjmp().
>
> >
> > -- Jeff J.
> >
> >
> > On Thu, Oct 12, 2023 at 5:39 AM Sebastian Huber
> > <sebastian.huber@embedded-brains.de
> > <mailto:sebastian.huber@embedded-brains.de>> wrote:
> >
> > On 06.10.23 07:31, Sebastian Huber wrote:
> > > Flush the windows in setjmp(). This helps if the stack is
> > changed after
> > > the setjmp() and we want to jump back to the original stack using
> > > longjmp().
> > > ---
> > > newlib/libc/machine/sparc/setjmp.S | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/newlib/libc/machine/sparc/setjmp.S
> > b/newlib/libc/machine/sparc/setjmp.S
> > > index 613df2ba2..d7185be4c 100644
> > > --- a/newlib/libc/machine/sparc/setjmp.S
> > > +++ b/newlib/libc/machine/sparc/setjmp.S
> > > @@ -110,6 +110,8 @@
> > >
> > > ENTRY(setjmp)
> > > ENTRY(_setjmp)
> > > + ta 0x03 /* Flush registers, just in case
> > another stack
> > > + is used after the setjmp().
> */
> > > st %sp, [%o0] /* caller's stack pointer */
> > > st %i7, [%o0+4] /* caller's return pc */
> > > st %fp, [%o0+8] /* store caller's frame pointer
> */
> >
> > I am not sure if there is anyone left being able to review this
> change.
> >
> > --
> > embedded brains GmbH
> > Herr Sebastian HUBER
> > Dornierstr. 4
> > 82178 Puchheim
> > Germany
> > email: sebastian.huber@embedded-brains.de
> > <mailto:sebastian.huber@embedded-brains.de>
> > phone: +49-89-18 94 741 - 16
> > fax: +49-89-18 94 741 - 08
> >
> > Registergericht: Amtsgericht München
> > Registernummer: HRB 157899
> > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas
> Dörfler
> > Unsere Datenschutzerklärung finden Sie hier:
> > https://embedded-brains.de/datenschutzerklaerung/
> > <https://embedded-brains.de/datenschutzerklaerung/>
> >
>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.huber@embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax: +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
>
next prev parent reply other threads:[~2023-10-12 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 5:31 Sebastian Huber
2023-10-12 9:39 ` Sebastian Huber
2023-10-12 14:50 ` Jeff Johnston
2023-10-12 14:55 ` Sebastian Huber
2023-10-12 15:33 ` Jeff Johnston [this message]
2023-10-12 15:19 ` Brian Inglis
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=CAOox84v8AvKsZqdW3wAn1GNvLw2oUY29ww0CqXLXXOF_4htfBQ@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).