On Tue, 2009-02-24 at 12:28 -0500, Marc Feeley wrote:
Could someone with a gcc 4.2 or 4.3 check that the new configure script (on the repository) detects these versions correctly and produces a message indicating that the -fno-move-loop-invariants option has been used automatically? Marc
With gcc-4.1.2 on a dual 2GHz G5 running Fedora 10, -fno-move-loop- invariants is not added to the command line and
[lucier@descartes gambc-v4_4_1-devel]$ ./configure CC=/pkgs/gcc-4.1.2/ bin/gcc --enable-single-host --enable-multiple-versions [lucier@descartes gambc-v4_4_1-devel]$ time make -j 2 505.369u 20.073s 4:52.24 179.7% 0+0k 128+132184io 0pf+0w
with gcc-4.3.2, -fno-move-loop-invariants is added to the command line and
[lucier@descartes gambc-v4_4_1-devel]$ ./configure --enable-single- host --enable-multiple-versions [lucier@descartes gambc-v4_4_1-devel]$ time make -j 2 281.834u 12.300s 2:35.83 188.7% 0+0k 0+101728io 0pf+0w
with gcc-4.3.2 and removing -fno-move-loop-invariants from the makefiles by hand:
[lucier@descartes gambc-v4_4_1-devel]$ time make -j 2 302.113u 14.224s 2:49.94 186.1% 0+0k 0+101784io 0pf+0w
With gcc-4.4.0, -fno-move-loop-invariants is not added to the command line and before the gcc fix went in
[lucier@descartes gambc-v4_4_1-devel]$ time make -j 2 450.618u 22.100s 4:09.31 189.6% 0+0k 1768+130864io 13pf+0w
and after the fix went in:
[lucier@descartes gambc-v4_4_1-devel]$ time make -j 2 434.837u 22.023s 4:04.33 186.9% 0+0k 0+130856io 0pf+0w
So it looks like the configure changes work. (And I wish 4.4 were faster, but it hasn't been released yet, so there's still hope ...)
Brad