> Note that the issue is with our representation of POINTER_PLUS_EXPR
> which insists on using sizetype for the pointer offset argument
> (where I don't remember if m32c uses a bigger or smaller mode for
> sizetype than for pointers).  Whenever the sizes of the modes for
> pointers and sizetype do not match we have a problem.
> 
> Note that while this particular issue may likely be fixed with
> the no-undefined-overflow branch work the above much general issue
> is _not_ fixed by it.

What about forbidding pointer induction variables completely if the
modes for sizetype and pointers do not match?

Paolo

Reply via email to