public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: newlib@sourceware.org, Kito Cheng <kito.cheng@sifive.com>,
	kito.cheng@gmail.com
Subject: Re: [PATCH] RISC-V: Support long double math
Date: Mon, 4 Dec 2023 21:47:12 +0800	[thread overview]
Message-ID: <CA+yXCZAMEhHLG0WGr625o3kGfBdD5VEoeSx_tspYobP27bGJFw@mail.gmail.com> (raw)
In-Reply-To: <ZW2dzrOt1xn3Q5Y7@calimero.vinschen.de>

Hi Corinna:

Thanks for reminding me, I didn't notice that since I just grabbed
from aarch64...:P [1]

Will check with upstream FreeBSD later :)

[1] https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/machine/aarch64/machine/_fpmath.h;h=fa62ae81cf19bf5b33637c6114f84f9910d17474;hb=HEAD


On Mon, Dec 4, 2023 at 5:37 PM Corinna Vinschen <vinschen@redhat.com> wrote:
>
> Hi Kito,
>
> thanks, both patches pushed.
>
> I just wonder...
>
> On Dec  4 15:41, Kito Cheng wrote:
> > diff --git a/newlib/libc/machine/riscv/machine/_fpmath.h b/newlib/libc/machine/riscv/machine/_fpmath.h
> > new file mode 100644
> > index 000000000..fa62ae81c
> > --- /dev/null
> > +++ b/newlib/libc/machine/riscv/machine/_fpmath.h
> > @@ -0,0 +1,64 @@
> > [...]
> > +union IEEEl2bits {
> > +     long double     e;
> > +     struct {
> > +             uint64_t        manl    :64;
> > +             uint64_t        manh    :48;
> > +             uint32_t        exp     :15;
> > +             uint32_t        sign    :1;
> > +     } bits;
> > +     /* TODO andrew: Check the packing here */
>
> ...if Andrew already checked the packaging, after he pushed this
> to the FreeBSD repo in 2015 :)))
>
>
> Thanks,
> Corinna
>

  reply	other threads:[~2023-12-04 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  7:41 Kito Cheng
2023-12-04  9:37 ` Corinna Vinschen
2023-12-04 13:47   ` Kito Cheng [this message]
2023-12-04 14:03     ` Corinna Vinschen

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=CA+yXCZAMEhHLG0WGr625o3kGfBdD5VEoeSx_tspYobP27bGJFw@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=newlib@sourceware.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).