From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] glibc update problem
Date: Tue, 28 Feb 2006 16:21:47 -0700 [thread overview]
Message-ID: <7573e9640602281521i5cf7ac39sbda9662f023a5c56@mail.gmail.com> (raw)
In-Reply-To: <20060228225750.7564725213F@smtp.nildram.co.uk>
On 2/28/06, Rupert Young (Restart) <rupert.young@restartconsulting.com> wrote:
> CFLAGS="-mtune=opteron -march=opteron -O3 -funroll-loops
> -fomit-frame-pointer -fprefetch-loop-arrays -pipe -ftracer -mmmx -msse
> -msse2 -m3dnow -mfpmath=sse"
Experimental CFLAGS. To quote the gcc documentation:
The following options control optimizations that may improve
performance, but are not enabled by any `-O' options. This section
includes experimental options that may produce broken code.
...
-ftracer
...
-fprefetch-loop-arrays
...
At a minimum, take these out and "emerge -Dev system". I would also
take out all of the mmx and sse flags, and let those be enabled by USE
flags for those packages where it is known to be safe to do so.
Finally, please turn off HTML email.
-Richard
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-28 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 22:57 [gentoo-amd64] glibc update problem Rupert Young (Restart)
2006-02-28 23:17 ` Boyd Stephen Smith Jr.
2006-02-28 23:21 ` Richard Fish [this message]
2006-02-28 23:26 ` Jan Riedel
2006-03-01 0:13 ` David Guerizec
2006-03-01 0:24 ` Will Briggs
2006-03-01 17:45 ` Hemmann, Volker Armin
2006-03-01 18:01 ` Simon Strandman
2006-03-02 0:08 ` [gentoo-amd64] " Duncan
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=7573e9640602281521i5cf7ac39sbda9662f023a5c56@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-amd64@lists.gentoo.org \
/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