public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.5.2-r7 build problems
Date: Thu, 12 Feb 2009 06:20:28 -0800	[thread overview]
Message-ID: <5bdc1c8b0902120620h76abf977if9eaf508905dd06@mail.gmail.com> (raw)
In-Reply-To: <20090212085859.73ff966e@krikkit>

On Thu, Feb 12, 2009 at 12:58 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 11 Feb 2009 20:22:32 -0800, Mark Knecht wrote:
>
>> > CFLAGS? The machine that fails:
>> >
>> > CFLAGS="-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe"
>
>> CFLAGS="-O2 -march=i686 -fomit-frame-pointer -pipe"
>
> You have more aggressive flags on the failing machine, have you tried
> using the more conservative (less ricey) flags?
>
>
> --
> Neil Bothwick

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 ?
-march=athlon-xp vs -march=i686
-funroll-loops
-fprefetch-loop-arrays
not using -fomit-frame-pointer

I would think that I should be able to also make the flags more
aggressive on a passing machine and see the same failure, assuming
this is the root cause.

Strange taht after 6-years this would come up but stranger thing happen.

Thanks,
Mark



  reply	other threads:[~2009-02-12 14:20 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 [this message]
2009-02-12 14:52               ` Mark Knecht
2009-02-12 17:34               ` Neil Bothwick

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=5bdc1c8b0902120620h76abf977if9eaf508905dd06@mail.gmail.com \
    --to=markknecht@gmail.com \
    --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