http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #2 from kevin.waugh at gmail dot com 2010-10-18 19:17:17 UTC --- (In reply to comment #1) > I think this is correct as __builtin_choose_expr still does semantically > checking on the two arguments. Not to mention __builtin_choose_expr was > added > only to support Altivec intrinsics and that has since been moved away from > that. >From the documentation: Note: This construct is only available for C. Furthermore, the unused expression (exp1 or exp2 depending on the value of const_exp) may still generate syntax errors. This may change in future revisions. What are the chances of getting this changed, or having an option to suppress warnings on the unevaluated argument? The implementation of tgmath.h is essentially using __builtin_choose_expr for the same purpose, but it appers to avoid any warnings/errors because of implicit casts.
