From: Jeff Kowing <jeffrey.d.kowing@nasa.gov>
To: robert.cole@support4linux.com
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] -pentium4 vs -pentium3
Date: Sat, 1 Mar 2003 15:22:26 -0600 [thread overview]
Message-ID: <15969.9362.40481.829880@igor.jsc.nasa.gov> (raw)
In-Reply-To: <200303010734.09181.robert.cole@support4linux.com>
Robert Cole writes:
> I recently noted a warning in the new make.conf file to not use the -pentium4
> compiler option and to use -pentium3 instead. My entire system was built from
> stage1 with -pentium4 and I'm not having any issues.
>
> To be safe I switched it to p3 for now.
>
> Anymore detail on this? Is this something that has to be fixed in gentoo
> specifically or all source in general?
Robert, I was bit by at least one of the problems a while back. It
seems that some of the floating point code is not quite right yet for
pentium4. I believe this is a gcc and maybe glibc issue. The
particular example that caused me problems is the glibc modf()
function. See
http://forums.gentoo.org/viewtopic.php?t=27211&highlight=python+float
for more info and a sample c program that will highlight the problem.
It was suggested at the time by Nick Jones (see
http://article.gmane.org/gmane.linux.gentoo.user/23056) that I back
down to pentium2. I haven't updated my portage recently, so I
haven't looked at what the new updated make.conf file suggests but I
definitely would follow any advice it gives.
--
Jeff Kowing
jeffrey.d.kowing@nasa.gov
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-03-01 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 15:34 [gentoo-dev] -pentium4 vs -pentium3 Robert Cole
2003-03-01 21:22 ` Jeff Kowing [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-02 14:37 Dhruba Bandopadhyay
2003-03-02 15:58 ` Riyad Kalla
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=15969.9362.40481.829880@igor.jsc.nasa.gov \
--to=jeffrey.d.kowing@nasa.gov \
--cc=gentoo-dev@gentoo.org \
--cc=robert.cole@support4linux.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