> Alan> BUG_ON(function(x,y)) > > #ifdef DEBUG > #define BUG_ON(x) if (x) BUG() > #else > #define BUG_ON(x) (void)(x) > #endif (void)(x) may cause x not be evaluated if the compiler can optimise it out on the grounds that the result is discarded. Fortunately gcc can't remove anything that has side effects so providing there are no other bugs in the code (eg referencing mmio addresses) it should be fine - you are correct - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Re: [PATCH]: 2.5.1pre9 change several if (x) BUG to BUG_ON(x)Momchil Velikov <velco _at_ fadata.bg>
- Prev by Date: Re: [kbuild-devel] Re: State of the new config & build system
- Next by Date: Re: O(1) scheduler, 2.5.2-pre9-B1 results
- Previous by thread: Re: [PATCH]: 2.5.1pre9 change several if (x) BUG to BUG_ON(x)
- Next by thread: [PATCH] Remove 8 bytes from struct page on 64bit archs
- Indexes:[Main][Thread]