From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] x87
Date: Mon, 2 Oct 2006 12:58:08 +0100 [thread overview]
Message-ID: <0b51d44d9fa58665417e8bda6bbbe66b@terzarima.net> (raw)
In-Reply-To: <1159552445.865081.235120@e3g2000cwe.googlegroups.com>
> Reading the article "The Various Ports", I get confused which the
> mention about the 387 float point unit. The libc compiled to x86
> machines use the fpu or not? If not how to make it work?
the system uses the fpu.
the 387 mentioned is built-in to x86 machines these days, often alongside
two or is it three others (3DNow! SSE SSE2). the compiler (and thus libc)
uses the 387 model.
the amd64 compiler uses sse2 instead.
next prev parent reply other threads:[~2006-10-02 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1159188606.358160.84860@i3g2000cwc.googlegroups.com>
2006-10-02 9:21 ` xspager
2006-10-02 11:58 ` Charles Forsyth [this message]
2006-10-02 19:21 ` erik quanstrom
2006-10-03 3:36 ` geoff
2006-10-03 8:06 ` erik quanstrom
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=0b51d44d9fa58665417e8bda6bbbe66b@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).