[PATCH] D37419: Teach scalar evolution to handle inttoptr/ptrtoint

[Daniel Berlin via llvm-commits]

>
>
> Sanjoy's description of the current behavior is accurate.
>



> I see two ways of looking at this:
>
>  1. This is a bug.
>  2. To allow this kind of inter-object addressing you need to use
> inttoptr/ptrtoint.
>
>
I'm fine with #2, i just feel like our rules are a little hodgepodge:)


> I don't believe that it is possible for the current behavior to manifest
> as a problem for C/C++ (and this is likely the same for most higher-level
> languages).
>

I don't believe it is either - we've already stated we assume aliasing does
not imply pointer equality and non-aliasing does not imply pointer
inequality.
If we did, this behaviour could.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170903/64371154/attachment.html>