This patch is intended to address PR22629. To copy from the bug report:
[from the bug report]
Consider this code:
int f(int x) { int a[] = {12}; return a[x]; }
GCC knows to optimize this to
movl $12, %eax ret
The code generated by recent Clang at -O3 is:
movslq %edi, %rax movl .L_ZZ1fiE1a(,%rax,4), %eax retq .L_ZZ1fiE1a: .long 12 # 0xc
[end from the bug report]
This definitely seems worth fixing. I've also seen this kind of code before (as the base case of generic vector wrapper templates with one element).
The general idea is to look at the GEP feeding a load or a store, which has some variable as its first non-zero index, and determine if that index must be zero (or else an out-of-bounds access would occur). We can do this for allocas and globals with constant initializers where we know the maximum size of the underlying object. When we find such a GEP, we create a new one for the memory access with that first variable index replaced with a constant zero.
Even if we can't eliminate the memory access (and sometimes we can't), it is still useful because it removes unnecessary indexing calculations.
Add a FIXME to hoist this into Analysis or somewhere it can be re-used? We should make it widely available. This is a great pattern to detect.