--- Comment #6 from rguenth at gcc dot gnu dot org 2008-01-06 09:56 ---
The problem is we have loads of unpartitionable SFTs. There are workarounds
possible that only might affect performance of generated code, for example
you can use --param salias-max-array-elements=0, which will redu
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-01-06 00:36
---
Confirmed: Some comparative timings with Intel and Sun compilers which also use
very little memory.
$ time gfc -c -O2 janus_slow.f90
real2m53.448s
user2m51.425s
sys 0m1.878s
$ time ifort -c -O2 janu
--- Comment #4 from jaydub66 at gmail dot com 2008-01-05 23:51 ---
But 800MB of memory is definitely *a lot* for such a small file!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34683
--- Comment #3 from jaydub66 at gmail dot com 2008-01-05 23:46 ---
(In reply to comment #2)
> Can you give the output of the compiler when -ftime-report is added?
Sure thing, thanks for the remark. Here it goes:
gfortran-4.3 -c -ftime-report -O1 -fstrict-aliasing Amplitudes.f90
Execut
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-01-05 23:37 ---
Can you give the output of the compiler when -ftime-report is added?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34683
--- Comment #1 from jaydub66 at gmail dot com 2008-01-05 23:36 ---
Created an attachment (id=14885)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14885&action=view)
test case
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34683
