[openbeos] Re: Test suite build issues

  • From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Mon, 09 Sep 2002 00:41:42 CEST (+0200)

> I had some problems with the gcc compiler in BeOS again - looks like 
> it 
> can compile BFS correctly only with -O1.
> 
> When looking over our Jamrules, I saw that the whole testing suite is 
> build with -O0 -g - but having made the experiences with a non-
> functional optimization in gcc, I would heavily suggest to not do 
> this 
> always.
> I would compile the test suite with the same compiler options as the 
> release build will, so that bugs caused by the compiler can also be 
> found in the future. At least, this would give us additional security 
> that gcc's output is correct. If some strange bugs show up, we can 
> always fall back to -g -O0 to fix them.

I think, it is usually desired to compile the tests with `-g'. And `-g' 
sort of implies `-O0'. IIRC the BFS tests are the only ones recompiling 
production code into the tests, while all other tests just link against 
the compiled code being compiled with whatever options desired.

While I'm rethinking the whole debug/warnings/options anyway (I have no 
completely satifying solution yet though), I guess, it won't harm to 
introduce a NO_TEST_DEBUG variable to turn off the current behavior 
(i.e. that the test rules override DEBUG and OPTIM). Would that be 
acceptable?

CU, Ingo



Other related posts: