From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.5.2-r7 build problems
Date: Thu, 12 Feb 2009 17:34:24 +0000 [thread overview]
Message-ID: <20090212173424.663d2725@krikkit> (raw)
In-Reply-To: <5bdc1c8b0902120620h76abf977if9eaf508905dd06@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
On Thu, 12 Feb 2009 06:20:28 -0800, Mark Knecht wrote:
> > You have more aggressive flags on the failing machine, have you tried
> > using the more conservative (less ricey) flags?
> I have not and intend to do that today. The flags have been set like
> this since 2003 so I'm surprised that it might be something like this
> but it's clearly possible.
>
> I'm unqualified to say what part of the differences is making this set
> more aggressive. Line by line what's your opinion?
>
> -O3 vs -O2 ?
Not much difference.
> -march=athlon-xp vs -march=i686
The former is better, providing you're using an AthlonXP.
> -funroll-loops
You only have to look at http://funroll-loops.org/ to know this is a bad
option...
> not using -fomit-frame-pointer
That's pretty safe, the frame-pointer isn't much use anyway if you're
compiling without debug symbols, which most build do by default.
> Strange taht after 6-years this would come up but stranger thing happen.
Indeed.
--
Neil Bothwick
Obscenity is the crutch of inarticulate motherfuckers.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-02-12 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 1:58 [gentoo-user] python-2.5.2-r7 build problems Mark Knecht
2009-02-12 2:25 ` Joshua D Doll
2009-02-12 2:40 ` Mark Knecht
2009-02-12 3:04 ` Joshua D Doll
2009-02-12 4:18 ` Mark Knecht
2009-02-12 4:22 ` Mark Knecht
2009-02-12 4:22 ` Mark Knecht
2009-02-12 8:58 ` Neil Bothwick
2009-02-12 14:20 ` Mark Knecht
2009-02-12 14:52 ` Mark Knecht
2009-02-12 17:34 ` Neil Bothwick [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=20090212173424.663d2725@krikkit \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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