Blue Swirl writes:
> On 3/15/10, Markus Armbruster wrote:
>> Blue Swirl writes:
>>
>> > When building with -DNDEBUG, assert(0) will not stop execution
>> > so it must not be used for abnormal termination.
>>
>>
>> For each case: are you sure the code does not recover after assert(0)?
>> Not
On 3/15/10, Markus Armbruster wrote:
> Blue Swirl writes:
>
> > When building with -DNDEBUG, assert(0) will not stop execution
> > so it must not be used for abnormal termination.
>
>
> For each case: are you sure the code does not recover after assert(0)?
> Not saying it does, just asking whe
Blue Swirl writes:
> When building with -DNDEBUG, assert(0) will not stop execution
> so it must not be used for abnormal termination.
For each case: are you sure the code does not recover after assert(0)?
Not saying it does, just asking whether you checked.
> Use cpu_abort() when in CPU contex
On Sat, Mar 13, 2010 at 04:56:03PM +0200, Blue Swirl wrote:
> When building with -DNDEBUG, assert(0) will not stop execution
> so it must not be used for abnormal termination.
>
> Use cpu_abort() when in CPU context, abort() otherwise.
>
> Signed-off-by: Blue Swirl
The CRIS parts look good, tha
When building with -DNDEBUG, assert(0) will not stop execution
so it must not be used for abnormal termination.
Use cpu_abort() when in CPU context, abort() otherwise.
Signed-off-by: Blue Swirl
---
block/vvfat.c | 20 ++--
hw/sh7750.c | 30 +
