public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34128] slow gfortran 4.x (library?) compared to g77 3.4
Date: Sun, 18 Nov 2007 08:37:00 -0000 [thread overview]
Message-ID: <20071118083701.26278.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34128-15355@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from burnus at gcc dot gnu dot org 2007-11-18 08:37 -------
> It's 64-bit only, and it appears to be a glibc bug: with glibc on x86_64,
> sinf((float) integer_variable) is slower than (float)sin((double)
> integer_variable).
Can it be that it has been fixed meanwhile? Using demo1.f on x86-64 (openSUSE
factory; glibc 2.6.1 (20070803), g77 3.3.5 20050117; gfortran 4.3.0 20071117;
AMD Athlon64 x2 4800+) I get the following timings with "-O2":
g77 gfortran
-m32 real(4) 0.408s 0.421s
-m64 real(4) 1.040s 0.589s
-m32 real(8) 0.411s 0.408s
-m64 real(8) 0.976s 0.968s
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34128
next prev parent reply other threads:[~2007-11-18 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 22:23 [Bug libfortran/34128] New: " mnoble at space dot mit dot edu
2007-11-17 0:08 ` [Bug fortran/34128] " fxcoudert at gcc dot gnu dot org
2007-11-17 22:35 ` bdavis at gcc dot gnu dot org
2007-11-17 22:42 ` fxcoudert at gcc dot gnu dot org
2007-11-18 8:37 ` burnus at gcc dot gnu dot org [this message]
2007-12-08 19:00 ` jvdelisle at gcc dot gnu dot org
2007-12-08 19:05 ` jvdelisle at gcc dot gnu dot org
2008-03-29 4:49 ` jvdelisle at gcc dot gnu dot org
2008-03-29 5:28 ` jvdelisle at gcc dot gnu dot org
2008-03-29 21:20 ` jvdelisle at gcc dot gnu dot org
2009-03-28 13:21 ` fxcoudert at gcc dot gnu dot 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=20071118083701.26278.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).