search for: d22793

Displaying 3 results from an estimated 3 matches for "d22793".

Did you mean: d22792
2016 Jul 26
2
Alias Analysis with inbound GEPs
...ias should only be returned when we can prove a partial overlap. Otherwise, MayAlias should be returned. > Shouldn’t the “inbounds” keyword mean that the access to sub-array is also in-bounds? > No. inbounds applies only to the whole object. Would this proposal help: https://reviews.llvm.org/D22793 <https://reviews.llvm.org/D22793> ? — Mehdi > I’m trying to reach “NoAlias” consensus between GEP1 and GEP2. > Did the original code come from C or C++? What are we modeling here? > > -Hal > > Thanks. > > Elena > > > > ----------------------...
2016 Jul 25
3
Alias Analysis with inbound GEPs
Hi, I'm checking aliasing of two pointers: %GEP1 = getelementptr inbounds %struct.s, %struct.s* %0, i64 0, i32 1, i64 %indvars.iv41, i64 %indvars.iv39 %GEP2 = getelementptr inbounds %struct.s, %struct.s* %0, i64 0, i32 16 The result I got is "PartialAlias" because the indices of the GEP1 are variable. Shouldn't the "inbounds" keyword mean that the access to
2016 Jul 19
4
RFC: inbounds on getelementptr indices for global splitting
Hi all, I'd like to propose an IR extension that allows the inbounds keyword to be attached to indices in a getelementptr constantexpr. By placing the inbounds keyword on an index, any pointer derived from the getelementptr outside of the bounds of the element referred to by that index, other than the pointer one past the end of the element, shall be treated as a poison value. The main