AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: sunjoong at gmail dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32391
--- Comment #1 from sunjoong at gmail dot com 2007-06-18 14:18 ---
Created an attachment (id=13727)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13727&action=view)
A legacy fortran77 program
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32391
--- Comment #2 from sunjoong at gmail dot com 2007-06-18 14:19 ---
Created an attachment (id=13728)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13728&action=view)
A input data file of TMalign
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32391
--- Comment #3 from sunjoong at gmail dot com 2007-06-18 14:20 ---
Created an attachment (id=13729)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13729&action=view)
A input data file of TMalign
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32391
--- 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
--- Comment #6 from sunjoong at gmail dot com 2007-06-18 16:07 ---
Thanks again, Tobias
$ uname -a
Linux newton 2.6.12-gentoo-r10 #1 Sun Sep 4 13:29:37 KST 2005 i686 Intel(R)
Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux
$ gfortran -v
Using built-in specs.
Target: i686-pc-linux-gnu
--- Comment #8 from sunjoong at gmail dot com 2007-06-18 17:26 ---
I checked which part of TMalign.f make optimizaton wrong;
In DP subroutine,
DO j=1,NSEQ2
DO i=1,NSEQ1
D=VAL(i-1,j-1)+SCORE(i,j)
H=VAL(i-1,j)
if(DIR(i-1,j))H=H+GAP_OPEN
--- Comment #9 from sunjoong at gmail dot com 2007-06-18 18:31 ---
I cut the bellow and made a new subroutine,
then another part did not change on '-O0' and '-O1';
D=VAL(i-1,j-1)+SCORE(i,j)
H=VAL(i-1,j)
if(DIR(i-1,j))H=H+GAP_OPEN
--- Comment #11 from sunjoong at gmail dot com 2007-06-18 18:47 ---
Yes, I agree that program is not beautiful
and I know the the array 'w' of 'u3b' subroutine problem;
I think the author of u3b use w(1) as pointer.
However,
the wrong generation of optimize
--- Comment #13 from sunjoong at gmail dot com 2007-06-18 20:24 ---
The '-ffloat-store' option works! Thank you.
However that gave me some quenstions;
Is that feature or bug?
There is many floating point operations of course.
Why the only one specific resion ma
--- Comment #16 from sunjoong at gmail dot com 2007-06-20 23:34 ---
Thank all of you.
I could understand what make it different.
There is no 'volatile' statement in fortran77 syntax of gfortran.
Of course, volatile is not fortran77 standard, I think,
but a certian impl
--- Comment #18 from sunjoong at gmail dot com 2007-06-21 03:27 ---
I appreciate kargl's comments; they were helpful.
I had known there is VOLATILE attribute in new Fortran standard
but I had worked with "LEGACY" fortran77 program!
I'll write C code if I shuld wri
--- Comment #20 from sunjoong at gmail dot com 2007-06-21 04:35 ---
$ gfortran -O1 -o TMalign TMalign.f
In file TMalign.f:2005
VOLATILE D
1
Error: Unclassifiable statement at (1)
(In reply to comment #19)
> You
--- Comment #22 from sunjoong at gmail dot com 2007-06-21 09:14 ---
I checked VOLATILE statement passing in gfortran 4.3 .
Unfortunately I had failed to buid gfortran (and gcc) 4.3 in my i686,
I only checked that passing with ia64 binary on another ia64 machine.
(There is no gfortran
14 matches
Mail list logo
