public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: "Steve Munroe" <sjmunroe@us.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
	GNU libc hacker <libc-hacker@sources.redhat.com>,
	"Peter Bergner" <bergner@us.ibm.com>
Subject: Re: [PATCH] Fix ppc64 test-fenv
Date: Fri, 11 Apr 2003 19:43:00 -0000	[thread overview]
Message-ID: <OF8B208622.2B72474E-ON86256D05.0069EFE9-86256D05.006C5C11@rchland.ibm.com> (raw)


Jakub Jelinek writes

> If the official kernel source contained a buggy prctl so that it is
unsafe
> to try prctl on kernels between 2.4.19 and 2.4.21, then
linux/configure.in
> needs to be changed for 2.4.21 the minimum required kernel version.
> Really, having glibc built without --enable-kernel switch just not work
> forever no matter what kernel it is running on is a bad idea.

prctl is not buggy. It either supports the feature or not. Your patch is OK
and should be integrated.

It just does not correct the fundamental problem. The 2.4.20 kernel does
not
initialize FE0|1 correctly for new processes lwp's. This disables FPE
raise,
until/unless this state is explicitely changed later.

The original fe_nomask.c hack (inherited from PPC32) to set FE0|1 was only
partially reliable on uniprocessors and unreliable on SMPs. That is why we
added the PR_SET_FPEXC feature. I feel that fe_nomask should either work
correctly or return ENOSYS. Your patch prevents test-fenv from seeing a
EINVAL.

The fix (both correct initial state for FE0|1 and the PR_SET_FPEXC feature
are in Marcelo's 2.4.21.pre tree and will be released with 2.4.21.



             reply	other threads:[~2003-04-11 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 19:43 Steve Munroe [this message]
2003-04-11 22:09 ` Roland McGrath
     [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
  -- strict thread matches above, loose matches on Subject: below --
2003-04-11 18:06 Jakub Jelinek

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=OF8B208622.2B72474E-ON86256D05.0069EFE9-86256D05.006C5C11@rchland.ibm.com \
    --to=sjmunroe@us.ibm.com \
    --cc=bergner@us.ibm.com \
    --cc=drepper@redhat.com \
    --cc=jakub@redhat.com \
    --cc=libc-hacker@sources.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).