From: Jeff Johnston <jjohnstn@redhat.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: [PATCH] powerpc/setjmp: Add 64-bit support
Date: Fri, 23 Sep 2022 15:29:10 -0400 [thread overview]
Message-ID: <CAOox84tW9DokGeech5snH9==cOc5-nkZ4rGNU8RidAFOnNiEMg@mail.gmail.com> (raw)
In-Reply-To: <ae1394cd-c5dc-0ae6-df41-6a6c3f898f96@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Thanks Sebastian for clarifying.
Feel free to push.
-- Jeff J.
On Fri, Sep 23, 2022 at 3:02 PM Sebastian Huber <
sebastian.huber@embedded-brains.de> wrote:
> Hello Jeff,
>
> On 23/09/2022 20:04, Jeff Johnston wrote:
> > Just a couple of questions/issues:
> >
> > 1. How did you arrive at 70 doubles and 43 doubles length values?
>
> the 70 is the final offset 432 + 16 + 96 == 544 plus 16 for the
> alignment divided by 8 (size of double). I checked this also with the
> debugger.
>
> The 43 is the final offset 232 + 8 + 96 == 336 plus 8 for the alignment
> divided by 8.
>
> > 2. It appears that __SPE__ is not accounted for in setjmp.h
>
> The SPE is only used in 32-bit processors without a FPU or Altivec unit.
> So, 256 bytes for the jmp_buf are enough.
>
> --
> 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/
>
>
prev parent reply other threads:[~2022-09-23 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:37 Sebastian Huber
2022-09-23 18:04 ` Jeff Johnston
2022-09-23 19:02 ` Sebastian Huber
2022-09-23 19:29 ` Jeff Johnston [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='CAOox84tW9DokGeech5snH9==cOc5-nkZ4rGNU8RidAFOnNiEMg@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).