Displaying 2 results from an estimated 2 matches for "pr32314".
Did you mean:
pr2314
2018 Jun 12
2
One more No-alias case on Alias analysis
...s sense. I think that we can go further looking at:
n == 2*idx
and, calling computeKnownBits on n and idx, then asking whether:
knownZeros(n) == (knownZeros(idx) << 1) | 1 and
knownOnes(n) == knownOnes(idx) << 1
(please note the comment in aliasSameBasePointerGEPs regarding avoiding
PR32314)
also, if we have more than one array access, we can have:
n - idx == m - idx
then we have:
n-m == 2*idx
and so we can check:
knownZeros(n-m) == (knownZeros(idx) << 1) | 1 and
knownOnes(n-m) == knownOnes(idx) << 1
Sadly, we don't have a good API to do the knownBits check on t...
2018 Jun 11
4
One more No-alias case on Alias analysis
Hello All,
I have met one may-alias case from llvm's alias analysis. The code
snippet is as following:
char buf[4];
void test (int idx) {
char *a = &buf[3 - idx];
char *b = &buf[idx];
*a = 1;
*b = 2;
}
I can see below output from alias set tracker for above code snippet.
Alias sets for function 'test':
Alias Set Tracker: 1 alias sets for 2 pointer values.