http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53957
Anthony Falzone <prop_design at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |prop_design at yahoo dot com
--- Comment #12 from Anthony Falzone <prop_design at yahoo dot com> ---
Hi Guys,
I'm the developer of PROP_DESIGN. I originally posted on the Google GCC
Graphite Group. Thanks Tobias for creating this bug and realizing the root
issue. I originally thought auto-parallelization would be of benefit.
However, I recently starting experimenting with the Intel Fortran compiler and
have found some things that may help you out. I have found Intel Fortran IPO,
auto-vectorization, and/or auto-parallelization are of no benefit to
PROP_DESIGN. I also found, as Tobias mentioned here, that gfortran creates
significantly slower executable files than Intel Fortran. I have narrowed it
down to just the basic optimizations. It does not have to do with anything
else. If you compare gfortran -03 optimizations versus Intel Fortran /O3
optimizations, you see a big difference. One case I ran shows about 38.65%
faster executable files, if you use Intel Fortran with /O3 optimizations
compared to gfortran with -O3 optimizations.
I have a measle AMD C-60 processor and use Windows 7 64-bit. I have tried many
other gfortran for Windows compilers in the past, but I'm currently using the
latest version of TDM-GCC. I have also tried Linux but am not currently using
it. I have not tried Intel Fortran on Linux.
I am not much of a programmer, so I can't say why gfortran -O3 is making slower
executable files than Intel Fortran /O3. Perhaps you guys would know. I
thought this information might help you out. If I can be of any help to you,
let me know. My website has the latest version of PROP_DESIGN. Polyhedron
refuses to update the version I sent them years ago. It would probably be
better if you used the latest version for testing your software.
Sincerely,
Anthony Falzone
http://propdesign.weebly.com/
