Re:Apple’s Bitcode Telegraphs Future CPU Plans
by DannyBee on Tuesday June 16, 2015 @05:44PM
(#9728895)
#define BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
https://scaryreasoner.wordpress.com/2009/02/28/checking-size...
There are many ways to make it perform different behavior at compile time (though admittedly, most are abuse). The above should compile error, but if you push sizeof evaluation, will not.
Re:Apple’s Bitcode Telegraphs Future CPU Plans
by TheLoneWolfling on Tuesday June 16, 2015 @06:48PM
(#9729177)
Better form, for certain definitions of better (works in global scope):
#define BUILD_BUG_ON(condition) extern int build_bug_on[!!(condition)-1]
I can see an issue with template instantiation in C++: for example, if a template uses SFINAE to specialize a template for types of certain sizes, that needs to be evaluated purely at the C++->LLVM stage of compilation.
What is the compile time part of C do you mean? sizeof(T) is evaluated at compile time of course, but it would still produce pseudocode like:
Of course, an optimizer would likely constant-fold that conditional expression to remove the branch entirely, but I'm having a difficult time seeing how one could perform different behavior at compile time with sizeof(T) in C.