On Sat, 1 Dec 2012, David Edelsohn wrote:
> Richard,
>
> The testcases assume default signed char and fail on systems with
> different semantics. I believe that both testcases need to declare c
> as signed char to consistently test the desired behavior, right?
Fixed as follows.
Richard.
2012-
Richard,
The testcases assume default signed char and fail on systems with
different semantics. I believe that both testcases need to declare c
as signed char to consistently test the desired behavior, right?
Thanks, David
On Tue, 27 Nov 2012, Richard Biener wrote:
> c-family/
> * c-gimplify.c (c_gimplify_expr): Gimplify self-modify expressions
> here and use a type with proper overflow behavior for types that would
> need to be promoted for the arithmetic.
The front-end changes are OK.
> *
This re-surrects Josephs patch to fix PR35634 - the fact that
the C frontend family does not properly promote the expression
operands of self-modify expressions. Accounting for this during
gimplification is indeed easiest (as long as fold isn't too clever
with the expressions in unpromoted form).
