public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sunjoong at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32391] Generate wrong optimization code from fortran 77
Date: Mon, 18 Jun 2007 15:08:00 -0000 [thread overview]
Message-ID: <20070618150837.29314.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32391-14714@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from sunjoong at gmail dot com 2007-06-18 15:08 -------
Thank you, Tobias
I had missunderstood the default optimization level for gfortran
but the issue exists, I think.
I had traced side effects of optimization levels for the legacy program;
-O0 level and -O1 level were different
but from -O1 to -O3 gave same (wrong) results on gfortran, g77 and g95.
I tested it with pgi fortran and got same (right) results.
I checked gfortran 4.0.4, 4.1.2 and 4.2.0.
I did not check gfortran 4.3.
2007/6/18, Tobias Burnus <burnus@net-b.de>:
> Sunjoong Lee wrote:
> > I had compiled a legacy fortran77 code and foud a bug;
> > $ gfortran -o TMalign TMalign.f
> > $ ./TMalign 1aquA.pdb 1avaC.pdb | grep ^Ali
> > Aligned length= 89, RMSD= 6.41, TM-score= 0.24257, ID=0.042
> > $ gfortran -O0 -o TMalign TMalign.f
> > $ ./TMalign 1aquA.pdb 1avaC.pdb | grep ^Ali
> > Aligned length= 91, RMSD= 6.35, TM-score=0.24762 , ID=0.024
> I find this difference very odd as "-O0" is the default optimization for
> gfortran. Other than that I get always the same result ("91") with all
> -O levels I tried with gfortran 4.3, 4.2.0, 4.1.3 and ifort.
>
> Which version of the compiler are you using on which platform. (Use
> "gfortran -v" to shows this information.)
> Can you also show what "alias gfortran" (or "type gfortran") shows? Just
> to make sure there is no alias which adds options.
>
> Tobias
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32391
next prev parent reply other threads:[~2007-06-18 15:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 14:12 [Bug fortran/32391] New: Default optimization (level 1) bug of loop optimization (maybe) sunjoong at gmail dot com
2007-06-18 14:19 ` [Bug fortran/32391] " sunjoong at gmail dot com
2007-06-18 14:19 ` sunjoong at gmail dot com
2007-06-18 14:20 ` sunjoong at gmail dot com
2007-06-18 15:08 ` sunjoong at gmail dot com [this message]
2007-06-18 15:38 ` [Bug fortran/32391] Generate wrong optimization code on fortran 77 dominiq at lps dot ens dot fr
2007-06-18 16:07 ` sunjoong at gmail dot com
2007-06-18 16:38 ` [Bug fortran/32391] Wrong code with optimization on i686-pc-linux-gnu burnus at gcc dot gnu dot org
2007-06-18 17:26 ` sunjoong at gmail dot com
2007-06-18 18:31 ` sunjoong at gmail dot com
2007-06-18 18:36 ` kargl at gcc dot gnu dot org
2007-06-18 18:47 ` sunjoong at gmail dot com
2007-06-18 19:16 ` kargl at gcc dot gnu dot org
2007-06-18 20:24 ` sunjoong at gmail dot com
2007-06-18 20:48 ` kargl at gcc dot gnu dot org
2007-06-19 8:11 ` pinskia at gcc dot gnu dot org
2007-06-20 23:34 ` sunjoong at gmail dot com
2007-06-21 2:24 ` kargl at gcc dot gnu dot org
2007-06-21 3:27 ` sunjoong at gmail dot com
2007-06-21 4:08 ` kargl at gcc dot gnu dot org
2007-06-21 4:35 ` sunjoong at gmail dot com
2007-06-21 4:55 ` kargl at gcc dot gnu dot org
2007-06-21 9:15 ` sunjoong at gmail dot com
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=20070618150837.29314.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).