public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: __setfpucw in glibc 2.0.7
Date: Sat, 24 Jul 1999 11:25:00 -0000	[thread overview]
Message-ID: <m3so6ducpw.fsf@cygnus.com> (raw)
In-Reply-To: <19990724180949.E954957B9@ocean.lucon.org>

hjl@lucon.org (H.J. Lu) writes:

> It is in glibc 2.0 and it is used by some programs.

And it never must have been used.

> Why don't we try to avoid the binary incompatibility as much as we
> can?

People must use the functions which are designed for it.

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com   `------------------------

  reply	other threads:[~1999-07-24 11:25 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
1999-07-24 11:25     ` Ulrich Drepper [this message]
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=m3so6ducpw.fsf@cygnus.com \
    --to=drepper@cygnus.com \
    --cc=hjl@lucon.org \
    --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).