This is the mail archive of the
mailing list for the GCC project.
Re: Bugs in 7/27 snapshot
- To: bgarcia at fore dot com, law at cygnus dot com
- Subject: Re: Bugs in 7/27 snapshot
- From: mrs at wrs dot com (Mike Stump)
- Date: Mon, 10 Aug 1998 09:28:16 -0700
- Cc: egcs-bugs at cygnus dot com
> Date: Mon, 10 Aug 1998 06:43:22 -0400 (EDT)
> From: "Brad M. Garcia" <firstname.lastname@example.org>
> To: Jeffrey A Law <email@example.com>
> cc: firstname.lastname@example.org
> On Thu, 6 Aug 1998, Jeffrey A Law wrote:
> I've never tried building the test programs. I am building
> cross-compilers, and was under the impression that the test suite
> didn't work very well for cross-compilers.
:-( It works very well for cross compilers, so let me corect that
notion. We use it all the time. What you're probably thinking of, is
it necessarily needs to know more about your environment in a cross
situation, and if you don't want to take the time to teach it about
your environment, then it plain just won't work at all.
Now, you ask, this is just a slight miswording, why am I jumping up
and down? Well, it is the dozens of other people on this list that
have been thinking of it, that might think it would be way to much
work to do cross testing after reading what you wrote.
The short primer on what you need to do cross testing well:
a `box' to do testing on
a power controller to cycle power when you hang the box
some way to get `into' the box.
If you're lucky and never hang the board, or if you have a way to
reset the testing environment without power cycling, then you don't
need the power controller.
I personally would love to see more testing and more cross testing
results, and more frequently.