This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: crash in 1.0.3a fortran compilation
- To: Craig Burley <burley at gnu dot org>
- Subject: Re: crash in 1.0.3a fortran compilation
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 22 Jul 1998 22:30:54 -0600
- cc: egcs at cygnus dot com, lindahl at cs dot virginia dot edu
- Reply-To: law at cygnus dot com
In message <199807220746.DAA21137@melange.gnu.org>you write:
> That's a good point. OT1H, there's apparently plenty of freely
> redistributable Fortran code out there that could be snarfed into
> the g77.f-torture suite. OTOH, that would make the `make check'
> phase of typical builds take *much* longer, and the distributions
> larger as well, and it's not clear (to me anyway) why that'd be okay
> while, at the same time, we don't snarf major C packages (like GNU
> Emacs, lynx, and so on ;-) into gcc.c-torture.
Right. Part of the idea behind c-torture is for tests to be small and
easily understandable. It keeps the testsuite from running "forever"
and when the time comes to actually analyze a bug, it's a whole lot
easier to work from a 10 line hunk of code than wander through the
megabytes of code for emacs, the linux kernel, etc :-)
It would be nice if f-torture had the same kind of goals -- especially
since some of us C folks have to look at them once in a while to fix
codegen bugs :-) :-) I'm more likely to understand a dozen or two lines
of fortran code than I am something bigger.
jeff