On Tue, Mar 07, 2017 at 01:07:27AM +0800, Christopher Li wrote:
> On Tue, Mar 7, 2017 at 12:43 AM, Luc Van Oostenryck
> <luc.vanoostenryck@xxxxxxxxx> wrote:
> >
> > With an example:
> > == C code ==
> > void *foo(int *p) { return p + 5; }
> >
> > == linearized code ==
> > foo:
> > .L0:
> > <entry-point>
> > add.64 %r2 <- %arg1, $20
> > cast.64 %r3 <- (64) %r2
> > ret.64 %r3
> >
> > == LLVM code from sparse-llvm ==
> > ; ModuleID = '<stdin>'
> > source_filename = "sparse"
> >
> > define i8* @foo(i32* %ARG1) {
> > L0:
> > %0 = getelementptr i32, i32* %ARG1, inttoptr (i64 20 to i32*)
> > %R3 = bitcast i32* %0 to i8*
> > ret i8* %R3
> > }
> >
>
>
> OK, good. Let's use this example.
> I am using clang to get the llvm bytecode. t.c is your example.
>
> clang -S -emit-llvm /tmp/t.c
> Here is output, compare the line I am pointing at:
> The indices should be 5 according clang's output.
> However sparse-llvm generate as 20 per your output
> if I am reading it correctly.
Absolutely.
-- Luc
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
