search for: pointer_

...x, you will get this: %Ptr = getelementptr [100 x int]* %Stack, long %X ; <[100 x int] *> Where what you really want is this: %Ptr = getelementptr [100 x int]* %Stack, long 0, long %X ; <int*> The deal with the initial zero is that it is specifying how to index _through the pointer_, which is often forgotten about. This allows LLVM to translate this C code: int *P = ... P = P + 1; into this LLVM code: %P.1 = ... %P.2 = getelementptr int* %P.1, long 1 This probably won't make sense the first time you see it. Take a look at: http://llvm.cs.uiuc.edu/docs/LangRef.html#i_...

While it is great that LLVM has an IR Verifier, its a little troublesome to use because it separates the point of detection from the source of the problem. That is, the verifier gets run on a module or function after its been built. By that point, the compiler's state has moved past the point at which the error was placed into the module or function. Trying to track down the source of the

Hi Stefanos, Attached the testcase. I tried to reduce it further, but the problem goes away when I remove the instructions further. There is a nested loop and the fault occurs while processing the inner loop (for.body) To reproduce the crash: opt -O3 testcase.ll -o out.ll > `groupChecks()` will only try to group pointers that are on the same alias set. If that’s true, the RT check