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: Fri, 09 Nov 2012 11:33:00 -0000	[thread overview]
Message-ID: <bug-54966-4-7acGsPJcAT@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 #10 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2012-11-09 11:33:37 UTC ---
I've repeated the tests again on a different machine and the result are the
same 
gcc version 4.8.0 20121108 (experimental) [trunk revision 193333] (GCC) 
at O3 lto degrades the performances in two cases, improves in another…
at O2 lto just degrades performance for two cases (different than O3) and does
not improve for the others
with Ofast the differences are even more dramatic

[innocent@vinavx0 bugs48]$ c++ -Ofast smatrix.ii -march=native -flto ; taskset
-c 2 ./a.out
size 5.  v1: time in cycles 14255.6
size 5.  v2: time in cycles 3699.28
size 5.  v3: time in cycles 3715.55
size 6.  v1: time in cycles 9179.85
size 6.  v2: time in cycles 1906.91
size 6.  v3: time in cycles 1812.73

[innocent@vinavx0 bugs48]$ c++ -Ofast smatrix.ii -march=native ; taskset -c 2
./a.out
size 5.  v1: time in cycles 13933.9
size 5.  v2: time in cycles 2125.56
size 5.  v3: time in cycles 1028.43
size 6.  v1: time in cycles 28168
size 6.  v2: time in cycles 3528.72
size 6.  v3: time in cycles 2533.5


c++ -O3 smatrix.ii -march=native;  taskset -c 2 ./a.out
size 5.  v1: time in cycles 13896.1
size 5.  v2: time in cycles 2107.25
size 5.  v3: time in cycles 1647.42
size 6.  v1: time in cycles 31095.6
size 6.  v2: time in cycles 3862.43
size 6.  v3: time in cycles 3510.14



c++ -O3 smatrix.ii -march=native -flto; ./a.out
size 5.  v1: time in cycles 16183.5
size 5.  v2: time in cycles 3696.15
size 5.  v3: time in cycles 3698.27
size 6.  v1: time in cycles 36323.5
size 6.  v2: time in cycles 2799.47
size 6.  v3: time in cycles 2705.73

[innocent@vinavx0 bugs48]$ taskset -c 2 ./a.out
size 5.  v1: time in cycles 16150.1
size 5.  v2: time in cycles 3718.54
size 5.  v3: time in cycles 3784.38
size 6.  v1: time in cycles 36326.3
size 6.  v2: time in cycles 2785.33
size 6.  v3: time in cycles 2714.69



c++ -O2 smatrix.ii -march=native -flto ;  taskset -c 2 ./a.out
size 5.  v1: time in cycles 13809.2
size 5.  v2: time in cycles 3999.39
size 5.  v3: time in cycles 4186.2
size 6.  v1: time in cycles 35057.3
size 6.  v2: time in cycles 4657.59
size 6.  v3: time in cycles 4766.62

c++ -O2 smatrix.ii -march=native;  taskset -c 2 ./a.out
size 5.  v1: time in cycles 11300.6
size 5.  v2: time in cycles 2877.27
size 5.  v3: time in cycles 2947.01
size 6.  v1: time in cycles 30520
size 6.  v2: time in cycles 4623.54
size 6.  v3: time in cycles 5287.95


  parent reply	other threads:[~2012-11-09 11:33 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 [this message]
2012-11-12 13:20 ` vincenzo.innocente at cern dot ch

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-7acGsPJcAT@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).