public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pacho at condmat1 dot ciencias.uniovi.es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45483] gcc-4.4.3: probably wrong optimization options chosen by "-march=native"
Date: Thu, 22 Sep 2011 20:49:00 -0000	[thread overview]
Message-ID: <bug-45483-4-bJ150DlTSC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45483-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45483

--- Comment #8 from Pacho Ramos <pacho at condmat1 dot ciencias.uniovi.es> 2011-09-22 20:47:04 UTC ---
It's still using generic in gcc-4.5, -march has moved from prescott to
pentium-m:
gcc-4.4: \_ /usr/libexec/gcc/i686-pc-linux-gnu/4.4.5/cc1 -quiet -
-D_FORTIFY_SOURCE=2 -march=prescott --param l1-cache-size=32 --param
l1-cache-line-size=64 --param l2-cache-size=2048 -mtune=generic -quiet
-dumpbase - -auxbase-strip /dev/null -o /tmp/ccpMToQG.s


gcc-4.5.3: \_ /usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/cc1 -quiet -
-D_FORTIFY_SOURCE=2 -march=pentium-m --param l1-cache-size=32 --param
l1-cache-line-size=64 --param l2-cache-size=2048 -mtune=generic -quiet
-dumpbase - -auxbase-strip /dev/null -o /tmp/cc11MaKg.s


Should I try with gcc-4.6 to see if it uses something different than "generic"
for mtune (or march has changed again)?


       reply	other threads:[~2011-09-22 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45483-4@http.gcc.gnu.org/bugzilla/>
2011-09-22 20:49 ` pacho at condmat1 dot ciencias.uniovi.es [this message]
2011-09-22 21:39 ` [Bug target/45483] gcc-4.4.3 and 4.5.3: " hjl.tools at gmail dot com
2011-09-22 22:36 ` pacho at condmat1 dot ciencias.uniovi.es
2011-09-22 23:05 ` pacho at condmat1 dot ciencias.uniovi.es
2011-09-24 15:54 ` hjl.tools at gmail dot com
2011-09-24 16:03 ` pacho at condmat1 dot ciencias.uniovi.es
2010-09-01 15:04 [Bug c/45483] New: gcc-4.4.3: " pacho at condmat1 dot ciencias dot uniovi dot es
2010-09-01 15:56 ` [Bug target/45483] " hjl dot tools at gmail dot com
2010-09-01 16:06 ` pacho at condmat1 dot ciencias dot uniovi dot es
2010-09-01 16:37 ` hjl dot tools at gmail dot com
2010-09-06 10:45 ` pacho at condmat1 dot ciencias dot uniovi dot es
2010-09-06 15:09 ` hjl dot tools at gmail dot com

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=bug-45483-4-bJ150DlTSC@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).