This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/29621] lapack runs into infinite loop with -03



------- Comment #10 from fkar at nemesis-project dot org  2006-10-27 23:39 -------
Starting from 
http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#Optimize-Options
I compiled both BLAS/LAPACK using the following compiler flags:

-fdefer-pop -fguess-branch-probability -fcprop-registers -fif-conversion
-fif-conversion2 -ftree-ccp -ftree-dce -ftree-dominator-opts -ftree-dse
-ftree-ter -ftree-lrs -ftree-sra -ftree-copyrename -ftree-fre -ftree-ch
-funit-at-a-time -fmerge-constants -fthread-jumps -fcrossjumping
-foptimize-sibling-calls -fcse-follow-jumps  -fcse-skip-blocks -fgcse 
-fgcse-lm  -fexpensive-optimizations -frerun-cse-after-loop  -fcaller-saves
-fpeephole2 -fschedule-insns  -fschedule-insns2 -fsched-interblock 
-fsched-spec -fregmove -fstrict-aliasing -fdelete-null-pointer-checks
-freorder-blocks  -freorder-functions -falign-functions  -falign-jumps
-falign-loops  -falign-labels -ftree-vrp -ftree-pre -finline-functions
-funswitch-loops -fgcse-after-reload

which (including -fdelayed-branch which I deliberately ommited since I got
complaints for not being supported on my platform), are set to be the default
flags turned on by -O3.
No infinitely looping was observed now for the above test cases, which means
that the bug(?) exists in some other flag(s) triggerred by -O3.


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]