From: Jakub Jelinek <jakub@redhat.com>
To: Roland McGrath <roland@redhat.com>, Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix ppc64 test-fenv
Date: Fri, 11 Apr 2003 18:06:00 -0000 [thread overview]
Message-ID: <20030411180652.GF16629@sunsite.ms.mff.cuni.cz> (raw)
Hi!
Unless ppc64 glibc is built with --enable-kernel=2.4.21 or higher
(without this switch 2.4.19 is assumed), it will fail test-fenv
no matter whatever kernel it is running on.
The following patch fixes it.
2003-04-11 Jakub Jelinek <jakub@redhat.com>
* sysdeps/unix/sysv/linux/powerpc/powerpc64/fe_nomask.c
(__fe_nomask_env): Try prctl even if __ASSUME_NEW_PRCTL_SYSCALL
is not defined, but the prctl constants are.
--- libc/sysdeps/unix/sysv/linux/powerpc/powerpc64/fe_nomask.c.jj 2003-03-06 12:26:24.000000000 -0500
+++ libc/sysdeps/unix/sysv/linux/powerpc/powerpc64/fe_nomask.c 2003-04-11 10:18:44.000000000 -0400
@@ -27,9 +27,15 @@
const fenv_t *
__fe_nomask_env (void)
{
-#ifdef __ASSUME_NEW_PRCTL_SYSCALL
+#if defined PR_SET_FPEXC && defined PR_FP_EXC_PRECISE
+ int result;
INTERNAL_SYSCALL_DECL (err);
- INTERNAL_SYSCALL (prctl, err, 2, PR_SET_FPEXC, PR_FP_EXC_PRECISE);
+ result = INTERNAL_SYSCALL (prctl, err, 2, PR_SET_FPEXC, PR_FP_EXC_PRECISE);
+# ifndef __ASSUME_NEW_PRCTL_SYSCALL
+ if (INTERNAL_SYSCALL_ERROR_P (result, err)
+ && INTERNAL_SYSCALL_ERRNO (result, err) == EINVAL)
+ __set_errno (ENOSYS);
+# endif
#else
__set_errno (ENOSYS);
#endif
Jakub
next reply other threads:[~2003-04-11 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 18:06 Jakub Jelinek [this message]
[not found] <OF5176686A.8C0180BF-ON86256D05.00655502-86256D05.00665397@rchland.ibm.com>
2003-04-11 18:50 ` Ulrich Drepper
2003-04-11 18:54 ` Jakub Jelinek
2003-04-11 19:43 Steve Munroe
2003-04-11 22:09 ` Roland McGrath
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=20030411180652.GF16629@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.com \
/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).