From: hjl@lucon.org (H.J. Lu)
To: drepper@cygnus.com
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: __setfpucw in glibc 2.0.7
Date: Sat, 24 Jul 1999 11:09:00 -0000 [thread overview]
Message-ID: <19990724180949.E954957B9@ocean.lucon.org> (raw)
In-Reply-To: <m3n1woe4j5.fsf@cygnus.com>
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > __setfpucw is the only function available in glibc 2.0.7
> > to control the FPU at the run-time. There is <fenv.h> in
> > glibc 2.1. But it is not available in glibc 2.0. I believe
> > we should export it in glibc 2.1.2.
>
> No. Nobody outside the libc should have used it. This function is
> not portable. Therefore people should have used asms which at least
> is portable on machines of the same architecure.
>
It is in glibc 2.0 and it is used by some programs. It
doesn't make any senses to break existing binaries. At
least, it should be global as the glibc 2.0 symbol
and local as the glibc 2.1 symbol so that ld won't use
it. People have been complaining about the Linux library
upgrade. Why don't we try to avoid the binary incompatibility
as much as we can?
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1999-07-24 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-22 14:03 H.J. Lu
1999-07-24 11:03 ` Ulrich Drepper
1999-07-24 11:09 ` H.J. Lu [this message]
1999-07-24 11:25 ` Ulrich Drepper
1999-07-24 12:06 ` Thorsten Kukuk
1999-07-24 12:58 ` H.J. Lu
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=19990724180949.E954957B9@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@cygnus.com \
--cc=libc-hacker@sourceware.cygnus.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).