On Wed, 8 Nov 2017, Jakub Jelinek wrote: > of course only if LVAL is false. Additionally, I've added folding of > "foo"[2] into 'o'. We have it in gimple-fold.c or so, so that one
Note that if the 2 there comes from an overflowing expression that's not valid as an extension to constant expressions in initializers (that is, static char c = "foo"[INT_MAX * -2]; should result in an error with -pedantic-errors because of the overflow, just as INT_MAX * -2 by itself wouldn't be a valid initializer in that case). > Not sure about the COND_EXPR/VEC_COND_EXPR cases, right now I'm passing > false as LVAL for the first operand (condition) and lval as LVAL for the > other two (i.e. if called with lval == true on the whole *_COND_EXPR > decl_constant_value_for_optimization etc. isn't performed on op1/op2, while > without it it is). Can one take address of the whole COND_EXPR, or > have it on LHS of anything in C? If not, perhaps I could just pass false > in all the 3 calls. Though, then likely it would be called with lval == false > anyway. Conditional and compound expressions are never valid lvalues in C. -- Joseph S. Myers jos...@codesourcery.com
