[Bug fortran/43463] large compile time regressions for Polyhedron 2005 benchmarks

2010-03-21 Thread steven at gcc dot gnu dot org
--- Comment #1 from steven at gcc dot gnu dot org 2010-03-21 09:57 --- How did you configure the compilers? (Think --enable-checking=release, etc.) -- steven at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/43463] large compile time regressions for Polyhedron 2005 benchmarks

2010-03-21 Thread howarth at nitro dot med dot uc dot edu
--- Comment #2 from howarth at nitro dot med dot uc dot edu 2010-03-21 14:36 --- Using built-in specs. COLLECT_GCC=gcc-4 COLLECT_LTO_WRAPPER=/sw/lib/gcc4.5/libexec/gcc/x86_64-apple-darwin10.3.0/4.5.0/lto-wrapper Target: x86_64-apple-darwin10.3.0 Configured with:

[Bug fortran/43463] large compile time regressions for Polyhedron 2005 benchmarks

2010-03-21 Thread howarth at nitro dot med dot uc dot edu
--- Comment #3 from howarth at nitro dot med dot uc dot edu 2010-03-21 18:40 --- Using built-in specs. Target: x86_64-apple-darwin10.3.0 Configured with: ../gcc-4.4.4/configure --prefix=/sw --prefix=/sw/lib/gcc4.4 --mandir=/sw/share/man --infodir=/sw/share/info

[Bug fortran/43463] large compile time regressions for Polyhedron 2005 benchmarks

2010-03-21 Thread steven at gcc dot gnu dot org
--- Comment #4 from steven at gcc dot gnu dot org 2010-03-21 19:04 --- Development branches have extra checking enabled, and it's always been like that. If you compile with -ftime-report, the compiler warns if the extra checking is enabled, and that's quite enough. -- steven at gcc