snapshot testsuite running bolix

snapshot testsuite running bolix

[David S. Miller]

If check-gcc encounters any unexpected errors, that stops make at the
end of running the gcc testsuite, thus it won't run check-g++ at all
and it must be invoked by hand.  I think this is incorrect.

Are others seeing this as well?

Later,
David "Sparc" Miller
davem@caip.rutgers.edu

Re: Questions about Haifa scheduler

[Allen Briggs]

> Are you just looking for performance information?  Or are you looking
> for technical information?  Regardless, this is the place to ask.

More for technical information--it's probably too early to get any
meaningful performance comparison (except possibly on the PPC model(s)
that the development team was working with).

> The m68k has no scheduling parameters defined, so the instruction
> scheduler will not do anything for 68k targets.

Heh...  That's a little surprising since it's been around for a while
and I thought a lot of folks were using gcc for 68k-based embedded
systems...

Maybe I'll look at this if I get bored (unlikely).  It's chalked on the
list, anyway.  I've been wanting to learn more about the gcc backend for
a while...

> The best benchmarking tool is always code you care about instead of
> synthetic benchmarks.

:-)  Of course...

Thanks for the responses, folks.

-allen

-- 
              Allen Briggs - end killing - briggs@macbsd.com

Re: snapshot testsuite running bolix

[David S. Miller]

   Date: Fri, 22 Aug 1997 13:40:43 -0400
   From: Ian Lance Taylor <ian@cygnus.com>

   check-gcc and check-g++ may be a special case, and it may be worth
   fixing the Makefile to check-g++ even if check-gcc fails.

I think they are, there is no reason that all testsuites should not
run because one fails, they are testsuites for crying out load ;-)

Re: snapshot testsuite running bolix

[Ian Lance Taylor]

   Date: Fri, 22 Aug 1997 13:17:27 -0400
   From: "David S. Miller" <davem@jenolan.rutgers.edu>

   If check-gcc encounters any unexpected errors, that stops make at the
   end of running the gcc testsuite, thus it won't run check-g++ at all
   and it must be invoked by hand.  I think this is incorrect.

I think it's a good idea in general for `make check' to return a valid
exit status.  Admittedly, the gcc testsuite pretty much always has at
least one failure.

To run multiple test suites, I use `make -k'.

check-gcc and check-g++ may be a special case, and it may be worth
fixing the Makefile to check-g++ even if check-gcc fails.

Ian