public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Prince <TimothyPrince@sbcglobal.net>
To: tomgogh20@yahoo.com
Cc: tprince@computer.org, gcc-help@gcc.gnu.org
Subject: Re: core2 flag for arch on gcc 4.3.2
Date: Sun, 28 Dec 2008 16:33:00 -0000	[thread overview]
Message-ID: <49579140.6030402@sbcglobal.net> (raw)
In-Reply-To: <869404.1220.qm@web31405.mail.mud.yahoo.com>

tom gogh wrote:
> Hi Tim,
>       sorry for not making it clear.
> I am building Gentoo 2008.0 and gcc supported is 4.1.2 which only
> supports -mnocona for core 2 duo processor.
> By migrating to gcc 4.3.2 I will get tunning for core 2 with flag
> -mcore2 but, it involves going to unsupported gcc for Gentoo.
> So, I want to know what is the difference between -mnocona flag of gcc
> versus -mcore2 flag of gcc 4.3.2. Is it worth in terms of speed
> optimization?
> 
You're still being unclear.  If you mean rebuilding an entire distro with
an up to date compiler, there may be reasons why it hasn't been done
already.  If you don't have any idea what kernel or glibc operations you
want to speed up, and how to measure it, and can't define what you mean by
worth while, I have no qualification to make that determination for you.
You give the impression that you haven't even compared the performance of
the compilers on applications which matter to you, or haven't even thought
about which applications matter.  gcc has made great advances since 4.1,
not only in optimizing for current CPU types, but in supporting OpenMP,
auto-vectorization, and current language standards.
Some of the more critical glibc operations are hand coded with inline asm,
so as to prevent gcc optimization from helping out.  If you choose not to
use an up to date memcpy(), for example, you can make it perform much
better by discarding the old glibc source and compiling C source with an
up to date gcc.  I don't know whether your gentoo uses up to date glibc,
but I would doubt it, if the recommended gcc is so old.

  reply	other threads:[~2008-12-28 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-28  5:23 tom gogh
2008-12-28 10:12 ` Tim Prince
2008-12-28 12:24   ` tom gogh
2008-12-28 16:33     ` Tim Prince [this message]
2008-12-28 18:40       ` tom gogh

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=49579140.6030402@sbcglobal.net \
    --to=timothyprince@sbcglobal.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tomgogh20@yahoo.com \
    --cc=tprince@computer.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).