Re: Problems with dejagnu and c++ tests...

Daniel Jacobowitz
2004-02-04T23:13:03Z

On Wed, Feb 04, 2004 at 06:03:42PM -0500, Michael Chastain wrote:
> > Which would mean that a GCC code-gen bug in malloc, or printf would
> > block all ability to run the testsuite :-(
>
> Ah, I see.
>
> So don't use printf ... use write(2).

I think assuming we can compile and run is fine. Output is an
absolutely no-show, however. Take a look at how many of our supported
targets don't have any kind of remote file I/O capability - gdbserver,
for one.

> There are 310 *.exp files in the test suite.
> 84 of them use get_compiler_info.
> 47 of them actually use one of the tests:
> test_compiler_info
> gcc_compiled, hp_aCC_compiler, hp_cc_compiler
> signed_keyword_not_used
>
> (Hmmm, I feel an obvious change coming to 37 files).
>
> 84 out of 310 is not even close to "all".
>
> If I did the compiler checks up front instead of inside get_compiler_info,
> then the compiler checks would have to do something nice if
> gdb_compile failed, such as leave compiler_info set to "no-compiler"
> for the language that failed.

And we'd save duplicating the tests 84 times...

--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer