Re: btest-gcc.sh patch ping and Re: Link tests after GCC_NO_EXECUTABLES

[Hans-Peter Nilsson <hp at bitrange dot com>]

On Mon, 3 Dec 2007, Geoff Keating wrote:
> On Dec 3, 2007, at 6:40 AM, Hans-Peter Nilsson <hp@bitrange.com> wrote:
> > 2 - btest-gcc.sh isn't updated to cover fortran.
> >   Patch at <http://gcc.gnu.org/ml/gcc-patches/2007-09/msg01710.html>.  Ping!
>
> Rejected; I do not think this script needs to be configurable in this fashion.

But *I* do.  As it doesn't affect the default functionality or
the integrity of the result (everything still listed in
build_log), and doesn't take away or add redundant
functionality, I don't really understand your rejection.

> If there's a log missing, and you think the underlying functionality is stable
> and well supported by GCC contributors on all platforms where it is enabled,
> propose a patch to add it.

The fortran tests are stable where it works, or so it seems.
Whether it works is port-specific (build issue on *-elf being
covered in this thread), and the patch above was a way to add
the functionality per-platform.  It would also allow e.g.
tracking gas or ld results in a combined tree.

I just need a regtest-script I can point to, such that people
can see how I build and regtest and possibly repeat it.  Your
btest-gcc.sh mostly fits, but not covering all gcc-related tests
that run by "make check" is really an issue.  I guess I could
solve that by adding a variant of that script in contrib/ though
I do prefer improving the existing one.

brgds, H-P