From: Ulrich Drepper <drepper@redhat.com>
To: buhr@stat.wisc.edu (Kevin Buhr)
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: RFC: changing precision control setting in initial FPU context
Date: 03 Mar 2001 16:45:44 -0800 [thread overview]
Message-ID: <m3d7byjr9j.fsf@otr.mynet.cygnus.com> (raw)
In-Reply-To: <E14ZLat-0004Js-00@the-village.bc.nu> <vban1b2ped5.fsf@mozart.stat.wisc.edu>
In-Reply-To: buhr@stat.wisc.edu's message of "03 Mar 2001 18:27:50 -0600"
buhr@stat.wisc.edu (Kevin Buhr) writes:
> > You want peoples existing applications to suddenely and magically change
> > their results. Umm problem.
>
> So, how would you feel about a mechanism whereby the kernel could be
> passed a default FPU control word by the binary (with old binaries, by
> default,
There will be no change whatsoever with me. The existing ABI is
fixed. If you want your programs to behave different set the mode
appropriately. I have not the slightest interest in seeing
applications (including the libc) being broken just because of this
stupid idea. No kernel and no libc modifications necessary. This is
the end of the story as far as I'm concerned.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
next prev parent reply other threads:[~2001-03-04 0:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 10:47 Adam J. Richter
2001-03-03 23:29 ` Kevin Buhr
2001-03-03 23:37 ` Alan Cox
2001-03-04 0:27 ` Kevin Buhr
2001-03-04 0:45 ` Ulrich Drepper [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-03 7:12 Kevin Buhr
2001-03-03 9:31 ` Albert D. Cahalan
2001-03-03 10:26 ` Kevin Buhr
2001-03-03 20:04 ` Albert D. Cahalan
2001-03-03 21:00 ` Jason Riedy
2001-03-03 23:17 ` Kevin Buhr
2001-03-04 4:21 ` Jason Riedy
2001-03-03 22:34 ` Kevin Buhr
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=m3d7byjr9j.fsf@otr.mynet.cygnus.com \
--to=drepper@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=buhr@stat.wisc.edu \
--cc=drepper@cygnus.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®