public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/54966] Does LTO requires a larger inline-unit-growth?
Date: Mon, 12 Nov 2012 13:20:00 -0000	[thread overview]
Message-ID: <bug-54966-4-12X3JZWy5E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54966-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #11 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2012-11-12 13:19:42 UTC ---
much better with 
gcc version 4.8.0 20121112 (experimental) [trunk revision 193427] (GCC) 
but for "size 6.  v1" with lto

[innocent@vinavx0 bugs48]$ c++ -Ofast smatrix.ii -march=native ; taskset -c 2
./a.out
size 5.  v1: time in cycles 6925.32
size 5.  v2: time in cycles 2123.49
size 5.  v3: time in cycles 1067.43
size 6.  v1: time in cycles 31216.7
size 6.  v2: time in cycles 3521.98
size 6.  v3: time in cycles 2523.74
[innocent@vinavx0 bugs48]$ c++ -Ofast smatrix.ii -march=native -flto; taskset
-c 2 ./a.out
size 5.  v1: time in cycles 6367.09
size 5.  v2: time in cycles 1181.97
size 5.  v3: time in cycles 1194.82
size 6.  v1: time in cycles 34811.5
size 6.  v2: time in cycles 1909.71
size 6.  v3: time in cycles 1803.48

of course inlining also the case "  v1" would be even better !(the code is
equivalent to v2 and v3)

I've some other more complex functions where inline is "different" than 4.7.2
but not necessarily better
will try to cut a test case


      parent reply	other threads:[~2012-11-12 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  6:29 [Bug lto/54966] New: " vincenzo.innocente at cern dot ch
2012-10-18  7:47 ` [Bug lto/54966] " dominiq at lps dot ens.fr
2012-10-18  9:44 ` rguenth at gcc dot gnu.org
2012-10-19  8:37 ` vincenzo.innocente at cern dot ch
2012-10-23 13:59 ` hubicka at ucw dot cz
2012-10-23 14:02 ` rguenther at suse dot de
2012-10-23 14:13 ` hubicka at ucw dot cz
2012-11-08 16:44 ` hubicka at gcc dot gnu.org
2012-11-09  6:39 ` vincenzo.innocente at cern dot ch
2012-11-09  6:52 ` vincenzo.innocente at cern dot ch
2012-11-09 11:33 ` vincenzo.innocente at cern dot ch
2012-11-12 13:20 ` vincenzo.innocente at cern dot ch [this message]

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-54966-4-12X3JZWy5E@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).