public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/31249] pseudo-optimzation with sincos/cexpi
Date: Sun, 18 Mar 2007 10:20:00 -0000	[thread overview]
Message-ID: <20070318102006.29386.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31249-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from dominiq at lps dot ens dot fr  2007-03-18 10:20 -------
Andrew,

Thanks for the answer. Additional timings for AMD Opteron(tm) Processor 250,
2.4Ghz:

Target: x86_64-unknown-linux-gnu
...
gcc version 4.3.0 20061231 (experimental)

[tocata] test/fortran> gfc -O3 sincos.f90 
[tocata] test/fortran> time a.out 
 -6.324121691031215E-002 -2.934957388823078E-003
19.847u 0.001s 0:20.41 97.2%    0+0k 0+0io 0pf+0w

[tocata] test/fortran> gfc -O3 sincos_o.f90
[tocata] test/fortran> time a.out
 -6.324121619598655E-002 -2.934957388823078E-003
19.793u 0.000s 0:19.80 99.9%    0+0k 0+0io 0pf+0w

[tocata] test/fortran> gfc -O3 cexp.f90 
[tocata] test/fortran> time a.out
 -6.324121619598655E-002 -2.934957388823078E-003
15.613u 0.000s 0:15.63 99.8%    0+0k 0+0io 0pf+0w

sin+cos is not optimized as cexpi.

Target: i386-pc-linux-gnu
...
gcc version 4.3.0 20070225 (experimental)

[tocata] test/fortran> gfc32 -Wa,-32 -O3 -fdump-tree-optimized sincos.f90
[tocata] test/fortran> time a.out
 -6.324122144403047E-002 -2.934963088285132E-003
10.757u 0.000s 0:10.76 99.9%    0+0k 0+0io 0pf+0w

[tocata] test/fortran> gfc32 -Wa,-32 -O3 -fdump-tree-optimized sincos_o.f90
tocata] test/fortran> time a.out 
 -6.324122124732012E-002 -2.934963117388848E-003
7.291u 0.001s 0:07.47 97.5%     0+0k 0+0io 4pf+0w

[tocata] test/fortran> gfc32 -Wa,-32 -O3 -fdump-tree-optimized cexp.f90
[tocata] test/fortran> time a.out
 -6.324122124732012E-002 -2.934963117388848E-003
11.412u 0.000s 0:11.41 100.0%   0+0k 0+0io 0pf+0w

sin+cos is optimized as cexpi which is faster than cexp -> real optimization!
The i386 code is almost twice as fast as the x86_64 one.


-- 


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


  parent reply	other threads:[~2007-03-18 10:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-17 21:11 [Bug middle-end/31249] New: " dominiq at lps dot ens dot fr
2007-03-18  9:50 ` [Bug middle-end/31249] " pinskia at gcc dot gnu dot org
2007-03-18 10:20 ` dominiq at lps dot ens dot fr [this message]
2007-03-19  9:28 ` dominiq at lps dot ens dot fr
2007-03-19 10:43 ` rguenth at gcc dot gnu dot org
2007-03-19 12:44 ` dominiq at lps dot ens dot fr
2007-03-19 17:52   ` Andrew Pinski
2007-03-19 17:53 ` pinskia at gmail dot com
2007-03-20 11:04 ` rguenth at gcc dot gnu dot org
2007-03-20 13:57 ` dominiq at lps dot ens dot fr
2007-03-20 14:03 ` dominiq at lps dot ens dot fr
2007-03-20 14:26 ` rguenth at gcc dot gnu dot org
2007-03-20 14:58 ` dominiq at lps dot ens dot fr
2007-03-20 15:07 ` rguenth at gcc dot gnu dot org
2007-03-20 16:09 ` dominiq at lps dot ens dot fr
2007-03-20 16:12 ` rguenth at gcc dot gnu dot org
2007-03-20 16:14 ` pinskia at gcc dot gnu dot org
2007-03-21 15:36 ` dominiq at lps dot ens dot fr
2007-03-21 15:57 ` rguenth at gcc dot gnu dot org
2007-03-21 16:09 ` dominiq at lps dot ens dot fr
2009-12-04 17:10 ` [Bug middle-end/31249] pseudo-optimization " dominiq at lps dot ens dot fr

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=20070318102006.29386.qmail@sourceware.org \
    --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).