From: hjl@lucon.org (H.J. Lu)
To: kukuk@suse.de (Thorsten Kukuk)
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: __setfpucw in glibc 2.0.7
Date: Sat, 24 Jul 1999 12:58:00 -0000 [thread overview]
Message-ID: <19990724195826.466EE57B9@ocean.lucon.org> (raw)
In-Reply-To: <19990724210532.A20628@Wotan.suse.de>
>
> As far as I know, on our 6 SuSE Linux 6.2 CDs is only one program
> which uses __setfpucw. And for this I use the same workaround as
> for the applixware binaries.
>
I was told quake used it.
--
H.J. Lu (hjl@gnu.org)
prev parent reply other threads:[~1999-07-24 12:58 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
1999-07-24 12:06 ` Thorsten Kukuk
1999-07-24 12:58 ` H.J. Lu [this message]
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=19990724195826.466EE57B9@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=kukuk@suse.de \
--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).