public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Gcc 4.3.4 ---> 4.4.1
Date: Sat, 15 Aug 2009 19:59:34 +0300	[thread overview]
Message-ID: <h66phg$58p$1@ger.gmane.org> (raw)
In-Reply-To: <5bdc1c8b0908150948t61b15d6dla93b149341a4cff0@mail.gmail.com>

On 08/15/2009 07:48 PM, Mark Knecht wrote:
> On Fri, Aug 14, 2009 at 5:43 PM, Nikos Chantziaras<realnc@arcor.de>  wrote:
>> [...]
>> I am doing an emerge -e system and emerge -e world anyway though since I
>> want to take advantage of the faster code 4.4 produces in general, but also
>> more specific whether or not the new "graphite" optimizer of GCC 4.4 (needs
>> "graphite" USE flag enabled for gcc) will give additional performance gain.
>>
>> (If anyone is interested in that, you need to first add:
>>
>>   -floop-interchange -floop-strip-mine -floop-block
>>
>> to CFLAGS/CXXFLAGS (the options enabling the Graphite optimizer) and then
>> "emerge -e" system and world.)
>
> Are there any Gentoo upgrade instructions for these flags or did you
> figure this out from other sources?

The upgrade instructions don't deal with CFLAGS.  The specific GCC flags 
are from GCC's documentation.  My CFLAGS were "-O2 -march=core2 -pipe" 
previously, and I just added to that the new GCC 4.4 graphite flags.


> If I was going to switch to 4.4
> seems like I'd want to get as much performance as I could safely get.

I'm afraid there's not enough testing on the graphite optimizer yet to 
tell if those flags are as safe as -O2.  In other words, you're on your own.


> I'm assuming that the list above is possibly not the complete list you
> might have in make.conf???

No, the complete list of CFLAGS/CXXFLAGS in my make.conf now is:

-march=core2 -O2 -floop-interchange -floop-strip-mine -floop-block -pipe

And that's it.  I was using very sane CFLAGS and I don't now if those 
three new "-floop" graphite flags count as "ricer CFLAGS" or not, since 
as I said previously, there's not enough testing yet :P




  reply	other threads:[~2009-08-15 16:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 23:17 [gentoo-user] Gcc 4.3.4 ---> 4.4.1 felix
2009-08-14 23:29 ` [gentoo-user] " walt
2009-08-15  0:33   ` felix
2009-08-15  0:43     ` Nikos Chantziaras
2009-08-15 16:48       ` Mark Knecht
2009-08-15 16:59         ` Nikos Chantziaras [this message]
2009-08-15 17:07       ` 7v5w7go9ub0o
2009-08-15 17:39         ` Nikos Chantziaras
2009-08-15 18:35           ` 7v5w7go9ub0o
2009-08-15 18:52             ` Nikos Chantziaras
2009-08-15 18:57               ` Nikos Chantziaras
2009-08-15 15:50     ` Alan McKinnon
2009-08-15 16:42       ` Mark Knecht
2009-08-15 16:49         ` Nikos Chantziaras
2009-08-15 17:10           ` Mark Knecht
2009-08-15 17:06         ` Dirk Heinrichs
2009-08-15 17:18           ` Mark Knecht
2009-08-15 17:28             ` Alan McKinnon
2009-08-15 17:24           ` Nikos Chantziaras
2009-08-15 17:37             ` Dirk Heinrichs
2009-08-15 17:40               ` Nikos Chantziaras
2009-08-16 12:43               ` Alan McKinnon
2009-08-15 17:25           ` Alan McKinnon
2009-08-15 17:39             ` Dirk Heinrichs
2009-08-15 17:17         ` Alan McKinnon
2009-08-15  7:22 ` [gentoo-user] " 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='h66phg$58p$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --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