[sdcc-devel] gcc-torture-execute tests

[Maarten B. <sou...@ds...>]

Hi Philippe,

I was wondering why all gcc-torture-execute tests that you added 
recently have this construction:

if (!some_test)
    ASSERT(0);

This defies half the purpose of the ASSERT macro: counting the tests and 
reporting what exactly failed. As it is now most tests report that 
nothing was tested. And when it does fail it only states that '0' failed 
so you have to find the cause by line number instead of text. Is there a 
special reason why you do not use:

ASSERT (some_test);

If there is none, please modify accordingly.

Greetings,
Maarten