HomePhabricator

[BasicAA] Remove checks for GEP decomposition limit reached

Authored by nikic on Sat, Nov 7, 10:02 AM.

Description

[BasicAA] Remove checks for GEP decomposition limit reached

The GEP aliasing code currently checks for the GEP decomposition
limit being reached (i.e., we did not reach the "final" underlying
object). As far as I can see, these checks are not necessary. It is
perfectly fine to work with a GEP whose base can still be further
decomposed.

Looking back through the commit history, these checks were originally
introduced in 1a444489e9d90915cfdda0720489893896ef1503. However, I
believe that the problem this was intended to address was later
properly fixed with 1726fc698ccb85fe4bb23c200a50f28b57fc53cb, and
the checks are no longer necessary since then (and were not the
right fix in the first place).

Differential Revision: https://reviews.llvm.org/D91010

Details

Committed
nikicThu, Nov 12, 11:43 AM
Differential Revision
D91010: [BasicAA] Remove checks for GEP decomposition limit reached
Parents
rGe7c7a1982632: [Frontend] Treat .cuh files as CUDA source files
Branches
Unknown
Tags
Unknown