This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
how to test library generation
- From: Tim Prince <tprince at myrealbox dot com>
- To: fortran at gcc dot gnu dot org
- Date: Sun, 28 Aug 2005 07:27:45 -0700
- Subject: how to test library generation
- Reply-to: tprince at computer dot org
I haven't yet understood how modifications in the .m4 files are
propagated, and how they should be tested. I haven't found any Make
option which causes changes in the m4 directory to be noticed.
I was concerned about propagating excessive source code unrolling into
the complex variants; is that a problem?
Much of the library will not build with gcc-4.1, except at default
options. I don't see much point in performance tests, without trying
normal options, such as
-march=nocona -O2 -funroll-loops
which provokes repeated gcc 4.1 internal errors (not in the part I have
been modifying).
gcc-4.0.2 is OK, but the library source which goes with that is
different, and I think 4.0.2 misses optimization found by 4.1
When people say they want to verify ability to bootstrap, is that only
with default options?