public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: Eshan dhawan <eshandhawan51@gmail.com>
Cc: Newlib <newlib@sourceware.org>, Gedare Bloom <gedare@rtems.org>
Subject: Re: [PATCH 0/1] Fenv support for SPARC
Date: Thu, 4 Jun 2020 14:14:39 -0500	[thread overview]
Message-ID: <CAF9ehCWs8kviKR7WUtQb1z5hJXom6uBHYuJou74fHyHbFybYqQ@mail.gmail.com> (raw)
In-Reply-To: <20200603233627.31827-1-eshandhawan51@gmail.com>

I should add that we although just tested on 32-bit SPARC (V7/V8),
it appears to have 64-bit (V9) support. Eshan plans to follow up with
a patch similar to add that which will be structurally similar to the
x86_64/i386 relationship for sharing the implementation.

--joel

On Wed, Jun 3, 2020 at 6:36 PM Eshan dhawan <eshandhawan51@gmail.com> wrote:

> The Patch adds fenv support for SPARC.
>
> The implemenation files are taken from NetBSD.
>
> Eshan dhawan (1):
>   SPARC fenv support
>
>  newlib/configure.host                       |   1 +
>  newlib/libc/machine/sparc/sys/fenv.h        |  85 +++++
>  newlib/libm/machine/configure.in            |   1 +
>  newlib/libm/machine/sparc/Makefile.am       |  21 ++
>  newlib/libm/machine/sparc/configure.in      |  11 +
>  newlib/libm/machine/sparc/feclearexcept.c   |   7 +
>  newlib/libm/machine/sparc/fegetenv.c        |   7 +
>  newlib/libm/machine/sparc/fegetexceptflag.c |   7 +
>  newlib/libm/machine/sparc/fegetround.c      |   7 +
>  newlib/libm/machine/sparc/feholdexcept.c    |   7 +
>  newlib/libm/machine/sparc/fenv.c            | 350 ++++++++++++++++++++
>  newlib/libm/machine/sparc/feraiseexcept.c   |   7 +
>  newlib/libm/machine/sparc/fesetenv.c        |   7 +
>  newlib/libm/machine/sparc/fesetexceptflag.c |   7 +
>  newlib/libm/machine/sparc/fesetround.c      |   7 +
>  newlib/libm/machine/sparc/fetestexcept.c    |   7 +
>  newlib/libm/machine/sparc/feupdateenv.c     |   7 +
>  17 files changed, 546 insertions(+)
>  create mode 100644 newlib/libc/machine/sparc/sys/fenv.h
>  create mode 100644 newlib/libm/machine/sparc/Makefile.am
>  create mode 100644 newlib/libm/machine/sparc/configure.in
>  create mode 100644 newlib/libm/machine/sparc/feclearexcept.c
>  create mode 100644 newlib/libm/machine/sparc/fegetenv.c
>  create mode 100644 newlib/libm/machine/sparc/fegetexceptflag.c
>  create mode 100644 newlib/libm/machine/sparc/fegetround.c
>  create mode 100644 newlib/libm/machine/sparc/feholdexcept.c
>  create mode 100644 newlib/libm/machine/sparc/fenv.c
>  create mode 100644 newlib/libm/machine/sparc/feraiseexcept.c
>  create mode 100644 newlib/libm/machine/sparc/fesetenv.c
>  create mode 100644 newlib/libm/machine/sparc/fesetexceptflag.c
>  create mode 100644 newlib/libm/machine/sparc/fesetround.c
>  create mode 100644 newlib/libm/machine/sparc/fetestexcept.c
>  create mode 100644 newlib/libm/machine/sparc/feupdateenv.c
>
> --
> 2.17.1
>
>

      parent reply	other threads:[~2020-06-04 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 23:36 Eshan dhawan
2020-06-03 23:36 ` [PATCH 1/1] SPARC fenv support Eshan dhawan
2020-07-02 10:14   ` Corinna Vinschen
2020-06-04 19:14 ` Joel Sherrill [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=CAF9ehCWs8kviKR7WUtQb1z5hJXom6uBHYuJou74fHyHbFybYqQ@mail.gmail.com \
    --to=joel@rtems.org \
    --cc=eshandhawan51@gmail.com \
    --cc=gedare@rtems.org \
    --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).