public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: maxim wexler <blissfix@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: CFLAGS "...-O3 -pipe" vs "...O2 <no pipe>"
Date: Tue, 10 Apr 2007 07:29:26 -0700 (PDT)	[thread overview]
Message-ID: <243934.33164.qm@web31714.mail.mud.yahoo.com> (raw)
In-Reply-To: <2fcf3fa50704090643k63373d2fsc6ec78d3cd8d6d85@mail.gmail.com>


--- Francisco Rivas <taken2k4@gmail.com> wrote:

> Hi all :D
> 
> I think what "-march=your_arch -O2" it's enough,
> because -O3 it's highest
> but have some details
> (http://gentoo-wiki.com/CFLAGS#-O2_or_-O3.3F). My
> guess is "-march=your_arch
> -O2". I was compiled my entire system with those
> flags and my applications
> no matter which have a very good functionality...
> 
> I hope give you some help to make your decision...
> 

Interesting. Just completed emerge -uvDN world using
the "-03 -pipe" cflags in make.conf for the PIII arch.
I noticed as the output scrolled by that the flags I
set were being used for all packages *except* gcc
which used "-02 -pipe". 

-mw


       
____________________________________________________________________________________
Get your own web address.  
Have a HUGE year through Yahoo! Small Business.
http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-04-10 14:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09  1:48 [gentoo-user] CFLAGS "...-O3 -pipe" vs "...O2 <no pipe>" maxim wexler
2007-04-09  1:57 ` Sascha Hlusiak
2007-04-09  5:47 ` Andrey Gerasimenko
2007-04-09  8:28   ` Neil Bothwick
2007-04-09 12:40 ` [gentoo-user] " Alexander Skwar
2007-04-09 13:43   ` Francisco Rivas
2007-04-10 14:29     ` maxim wexler [this message]
2007-04-10 14:58       ` Uwe Thiem
2007-04-10 15:17         ` Bo Ørsted Andresen
2007-04-10 15:29         ` Francisco Rivas
2007-04-10 15:55           ` Tony Stohne
2007-04-10 16:40             ` Andrey Vul
2007-04-10 18:48               ` maxim wexler
2007-04-10 19:01                 ` Francisco Rivas
2007-04-10 19:10                   ` Davi
2007-04-10 19:45                     ` Uwe Thiem
2007-04-10 19:50                       ` Bo Ørsted Andresen
2007-04-10 19:56                       ` Jesús Guerrero
2007-04-10 20:08                         ` Davi
2007-04-10 20:15                           ` Jesús Guerrero
2007-04-10 20:24                             ` Davi
2007-04-10 22:03                               ` Ryan Sims
2007-04-11  0:34                                 ` Davi
2007-04-11 10:02                           ` [gentoo-user] " Alexander Skwar
2007-04-10 21:22                         ` [gentoo-user] " Uwe Thiem
2007-04-10 21:08                       ` Dan Farrell
2007-04-10 19:52                     ` Renat Golubchyk
2007-04-10 19:39                 ` Uwe Thiem
2007-04-11  9:39                 ` Daniel Iliev
2007-04-11 10:08                   ` Bo Ørsted Andresen
2007-04-11 10:56                     ` Daniel Iliev
2007-04-11 11:05                       ` Davi
2007-04-11 11:44                       ` Bo Ørsted Andresen
2007-04-11 12:37                         ` Francisco Rivas
2007-04-11 12:45                         ` Daniel Iliev
2007-04-10 15:29       ` Jesús Guerrero

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=243934.33164.qm@web31714.mail.mud.yahoo.com \
    --to=blissfix@yahoo.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