From: Stafford Horne <shorne@gmail.com>
To: GLIBC patches <libc-alpha@sourceware.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/4] OpenRISC fixes for 2.39
Date: Tue, 19 Mar 2024 21:42:40 +0000 [thread overview]
Message-ID: <20240319214244.736981-1-shorne@gmail.com> (raw)
I am preparing to get OpenRISC hard-float patches ready for upsteam and took
some time to make sure all the nofpu port tests are clean. Running the latest
tests I found a few issues. This series contains a few fixes for these issues.
Also, during reviewing the Linux signal ABI after Linux floating point support
went upstream I found the OpenRISC ucontext definition is missing one field.
This series includes a fix the this ucontext ABI breakage.
Stafford Horne (4):
or1k: Fix Linux user space signal ABI
or1k: Update libm test ulps
or1k: Only define fpu rouding and exceptions with hard-float
or1k: Add prctl wrapper to unwrap variadic args
sysdeps/or1k/bits/fenv.h | 19 ++++++++++
sysdeps/or1k/libm-test-ulps | 1 +
sysdeps/unix/sysv/linux/or1k/prctl.c | 42 +++++++++++++++++++++
sysdeps/unix/sysv/linux/or1k/sys/ucontext.h | 1 +
4 files changed, 63 insertions(+)
create mode 100644 sysdeps/unix/sysv/linux/or1k/prctl.c
--
2.44.0
next reply other threads:[~2024-03-19 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 21:42 Stafford Horne [this message]
2024-03-19 21:42 ` [PATCH 1/4] or1k: Fix Linux user space signal ABI Stafford Horne
2024-03-20 13:24 ` Adhemerval Zanella Netto
2024-03-20 14:13 ` Stafford Horne
2024-03-20 20:12 ` Adhemerval Zanella Netto
2024-03-19 21:42 ` [PATCH 2/4] or1k: Update libm test ulps Stafford Horne
2024-03-19 21:42 ` [PATCH 3/4] or1k: Only define fpu rouding and exceptions with hard-float Stafford Horne
2024-03-19 21:42 ` [PATCH 4/4] or1k: Add prctl wrapper to unwrap variadic args Stafford Horne
2024-03-20 13:28 ` Adhemerval Zanella Netto
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=20240319214244.736981-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-openrisc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.