public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46900] [4.6 Regression] 50% slowdown when linking with LTO in a single step
Date: Thu, 16 Dec 2010 15:24:00 -0000	[thread overview]
Message-ID: <bug-46900-4-fSihXGIvWO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46900-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-12-16 15:23:40 UTC ---
I think that the files passed to lto1 are the same - but I get different
command-line options:


a) Two-step compile with "-fexternal-blas -flto -Ofast -march=native"

x86_64-unknown-linux-gnu/4.6.0/lto1 -march=k8-sse3 -msahf --param
l1-cache-size=64 --param l1-cache-line-size=64 --param l2-cache-size=1024
-mtune=k8


b) Single-step compile:

x86_64-unknown-linux-gnu/4.6.0/lto1 -quiet -dumpbase ccmRjX1L.ltrans0.o
-mtune=generic -march=x86-64


Thus, the "-march=native" somehow gets lost in the single-step compile.


  parent reply	other threads:[~2010-12-16 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 10:31 [Bug fortran/46900] New: " burnus at gcc dot gnu.org
2010-12-12 10:33 ` [Bug middle-end/46900] " burnus at gcc dot gnu.org
2010-12-12 10:34 ` burnus at gcc dot gnu.org
2010-12-12 10:39 ` [Bug middle-end/46900] [4.6 Regression] " burnus at gcc dot gnu.org
2010-12-12 10:50 ` burnus at gcc dot gnu.org
2010-12-16 14:40 ` rguenth at gcc dot gnu.org
2010-12-16 15:24 ` burnus at gcc dot gnu.org [this message]
2010-12-17 12:14 ` d.g.gorbachev at gmail dot com
2011-01-19 17:10 ` rguenth at gcc dot gnu.org
2011-01-19 22:11 ` burnus at gcc dot gnu.org

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-46900-4-fSihXGIvWO@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).