From: Eshan dhawan <eshandhawan51@gmail.com>
To: newlib@sourceware.org
Cc: jeol@rtems.org, gedare@rtems.org, Eshan dhawan <eshandhawan51@gmail.com>
Subject: [PATCH 0/1] Add fenv support for ARM
Date: Wed, 3 Jun 2020 23:15:08 +0530 [thread overview]
Message-ID: <20200603174509.18606-1-eshandhawan51@gmail.com> (raw)
This Patch adds Fenv support for ARM.
The implementation files are taken from FreeBSD.
The files are added to libm/machine/arm
and libc/machine/arm
Eshan dhawan (1):
fenv support arm
newlib/libc/machine/arm/machine/acle-compat.h | 182 ++++++++++
newlib/libc/machine/arm/machine/fenv-mangle.h | 53 +++
.../libc/machine/arm/machine/fenv-softfloat.h | 187 ++++++++++
newlib/libc/machine/arm/machine/fenv-vfp.h | 187 ++++++++++
newlib/libc/machine/arm/sys/fenv.h | 122 +++++++
newlib/libm/machine/arm/Makefile.am | 18 +-
newlib/libm/machine/arm/fe_dfl_env.c | 7 +
newlib/libm/machine/arm/feclearexcept.c | 7 +
newlib/libm/machine/arm/fegetenv.c | 7 +
newlib/libm/machine/arm/fegetexceptflag.c | 7 +
newlib/libm/machine/arm/fegetround.c | 7 +
newlib/libm/machine/arm/feholdexcept.c | 7 +
newlib/libm/machine/arm/fenv-softfp.c | 32 ++
newlib/libm/machine/arm/fenv-vfp.c | 32 ++
newlib/libm/machine/arm/fenv.c | 328 ++++++++++++++++++
newlib/libm/machine/arm/feraiseexcept.c | 7 +
newlib/libm/machine/arm/fesetenv.c | 7 +
newlib/libm/machine/arm/fesetexceptflag.c | 7 +
newlib/libm/machine/arm/fesetround.c | 7 +
newlib/libm/machine/arm/fetestexcept.c | 7 +
newlib/libm/machine/arm/feupdateenv.c | 7 +
21 files changed, 1224 insertions(+), 1 deletion(-)
create mode 100644 newlib/libc/machine/arm/machine/acle-compat.h
create mode 100644 newlib/libc/machine/arm/machine/fenv-mangle.h
create mode 100644 newlib/libc/machine/arm/machine/fenv-softfloat.h
create mode 100644 newlib/libc/machine/arm/machine/fenv-vfp.h
create mode 100644 newlib/libc/machine/arm/sys/fenv.h
create mode 100644 newlib/libm/machine/arm/fe_dfl_env.c
create mode 100644 newlib/libm/machine/arm/feclearexcept.c
create mode 100644 newlib/libm/machine/arm/fegetenv.c
create mode 100644 newlib/libm/machine/arm/fegetexceptflag.c
create mode 100644 newlib/libm/machine/arm/fegetround.c
create mode 100644 newlib/libm/machine/arm/feholdexcept.c
create mode 100644 newlib/libm/machine/arm/fenv-softfp.c
create mode 100644 newlib/libm/machine/arm/fenv-vfp.c
create mode 100644 newlib/libm/machine/arm/fenv.c
create mode 100644 newlib/libm/machine/arm/feraiseexcept.c
create mode 100644 newlib/libm/machine/arm/fesetenv.c
create mode 100644 newlib/libm/machine/arm/fesetexceptflag.c
create mode 100644 newlib/libm/machine/arm/fesetround.c
create mode 100644 newlib/libm/machine/arm/fetestexcept.c
create mode 100644 newlib/libm/machine/arm/feupdateenv.c
--
2.17.1
next reply other threads:[~2020-06-03 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 17:45 Eshan dhawan [this message]
2020-06-03 17:45 ` [PATCH 1/1] fenv support arm Eshan dhawan
2020-07-02 12:11 ` Szabolcs Nagy
2020-07-02 15:48 ` Joel Sherrill
2020-07-02 22:33 ` Joel Sherrill
2020-07-03 9:14 ` Szabolcs Nagy
2020-07-03 13:12 ` Joel Sherrill
2020-06-10 1:15 ` [PATCH 0/1] Add fenv support for ARM Jeff Johnston
2020-06-10 17:31 ` Sebastian Huber
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=20200603174509.18606-1-eshandhawan51@gmail.com \
--to=eshandhawan51@gmail.com \
--cc=gedare@rtems.org \
--cc=jeol@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).