search for: add3

Hi LLVMdev, Does the latest trunk code support Windows Phone 8.1 target ? I was trying out a simple program, but Visual Studio 2013's linker failed for me with this error - app.obj : error LNK2008: Fixup target is not aligned 'add3' This is what I tried - * Download latest LLVM sources (as on 4th June) and build them on my MAC 10.9 machine. * Wrote a simple a.c, with add3 function- int add3(int i, int j) { int k = i+j; return k; } * Create LLVM IR using Xcode 5.1's clang (clang -S -O0 -emit-llvm a.c)...

...8.1 > > Hi LLVMdev, > > Does the latest trunk code support Windows Phone 8.1 target ? I don't know this, but ... > I was trying out a simple program, but Visual Studio 2013’s linker > failed for me with this error - app.obj : error LNK2008: Fixup target is > not aligned ‘add3' > > This is what I tried - > > * Download latest LLVM sources (as on 4th June) and build them on my > MAC 10.9 machine. > * Wrote a simple a.c, with add3 function- > > int add3(int i, int j) > { > int k = i+j; > return k; > } > > * Create LLV...

...ubject: Support for Windows Phone 8.1 Hi LLVMdev, Does the latest trunk code support Windows Phone 8.1 target ? I don't know this, but ... I was trying out a simple program, but Visual Studio 2013’s linker failed for me with this error - app.obj : error LNK2008: Fixup target is not aligned ‘add3' This is what I tried - * Download latest LLVM sources (as on 4th June) and build them on my MAC 10.9 machine. * Wrote a simple a.c, with add3 function- int add3(int i, int j) { int k = i+j; return k; } * Create LLVM IR using Xcode 5.1’s clang ( *clang –S -O0 -emit–llvm a.c* )...

Hi, I am trying to understand the semantics of Instructions in llvm. Are the following instructions semantically same? * %add2 = add nsw i32 %add, %add1 %add3 = add i32 %add, %add1* Based on my understanding from the Language Reference Manual, I think they are different. But then why is the *gvn* pass detecting *%add3* as redundant and deleting it? Your views are appreciated. Rekha -- Rekha -------------- next part -------------- An HTML attach...

...im Northover <t.p.northover at gmail.com> >> wrote: >> >>> On 23 July 2014 06:25, Rekha R <rekharamapai at nitc.ac.in> wrote: >>> > Are the following instructions semantically same? >>> > %add2 = add nsw i32 %add, %add1 >>> > %add3 = add i32 %add, %add1 >>> > >>> > Based on my understanding from the Language Reference Manual, I think >>> they >>> > are different. But then why is the gvn pass detecting %add3 as >>> redundant and deleting it? >>> >>>...

...ype is guaranteed to be big enough; or (as in C) by trusting the programmer to make sure that doesn't happen. > What are the redundancies in the following code snip. Assume they appear in > that order in a basic block. > > Case1; %add2 = add nsw i32 %add, %add1 > %add3 = add i32 %add, %add1 > > Case2: %add2 = add i32 %add, %add1 > %add3 = add nsw i32 %add, %add1 In both cases the add with nsw can be removed in favour of the one without. Order is completely irrelevant for normal LLVM arithmetic instructions. Cheers. Tim.

...ot overflow. On Wed, Jul 23, 2014 at 3:32 PM, Tim Northover <t.p.northover at gmail.com> wrote: > On 23 July 2014 06:25, Rekha R <rekharamapai at nitc.ac.in> wrote: > > Are the following instructions semantically same? > > %add2 = add nsw i32 %add, %add1 > > %add3 = add i32 %add, %add1 > > > > Based on my understanding from the Language Reference Manual, I think > they > > are different. But then why is the gvn pass detecting %add3 as redundant > and deleting it? > > On their common domain, the two instructions coincide....

...t; I don't know this, but ... >>> >>> I was trying out a simple program, but Visual Studio 2013¹s >>>linker >>> failed for me with this error - app.obj : error LNK2008: Fixup >>> target is >>> not aligned Œadd3' >>> >>> This is what I tried - >>> >>> * Download latest LLVM sources (as on 4th June) and build them >>> on my >>> MAC 10.9 machine. >>> * Wrote a simple a.c, with add3 function- >>&gt...

...%add1, %for.body ] %add = add nsw i32 %j.01, %i.03 %add1 = add nsw i32 %add, 1 %add2 = add nsw i32 %s.02, %add1 %inc = add nsw i32 %i.03, 1 %cmp = icmp slt i32 %i.03, 99 br i1 %cmp, label %for.body, label %for.end for.end: ; preds = %for.body %add3 = add nsw i32 %add2, %add1 ret i32 %add3 } the value range pass was not able to determine any size, even of the induction variable, is it a correct behavior? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/...

...LLVMdev, Does the latest trunk code support Windows Phone 8.1 target ? I don't know this, but ... I was trying out a simple program, but Visual Studio 2013¹s linker failed for me with this error - app.obj : error LNK2008: Fixup target is not aligned Œadd3' This is what I tried - * Download latest LLVM sources (as on 4th June) and build them on my MAC 10.9 machine. * Wrote a simple a.c, with add3 function- int add3(int i, int j) { int k = i+j; return k; } * Cr...

dear R experts: does R have "static" variables that are local to functions? I know that they are usually better avoided (although they are better than globals). However, I would like to have a function print how often it was invoked when it is invoked, or at least print its name only once to STDOUT when it is invoked many times. possible without <<- ? sincerely, /iaw

...dows Phone 8.1 target ? >> I don't know this, but ... >> I was trying out a simple program, but Visual Studio 2013¹s >> linker >> failed for me with this error - app.obj : error LNK2008: Fixup >> target is >> not aligned Œadd3' >> This is what I tried - >> * Download latest LLVM sources (as on 4th June) and build them >> on my >> MAC 10.9 machine. >> * Wrote a simple a.c, with add3 function- >> int add3(int i, int j) >>...

...32 %n) #0 {entry: %0 = load i32* %a, > align 4, !tbaa !1 %arrayidx1 = getelementptr inbounds i32* %a, i32 1 %1 = > load i32* %arrayidx1, align 4, !tbaa !1 %add = add nsw i32 %1, %0 > %arrayidx2 = getelementptr inbounds i32* %a, i32 2 %2 = load i32* > %arrayidx2, align 4, !tbaa !1 %add3 = add nsw i32 %add, %2 %arrayidx4 = > getelementptr inbounds i32* %a, i32 3 %3 = load i32* %arrayidx4, align 4, > !tbaa !1 %add5 = add nsw i32 %add3, %3 %arrayidx6 = getelementptr > inbounds i32* %a, i32 4 %4 = load i32* %arrayidx6, align 4, !tbaa !1 > %add7 = add nsw i32 %add5, %4...

...* nocapture %sum) #0 { entry: %0 = load i32* %a, align 4, !tbaa !1 %arrayidx1 = getelementptr inbounds i32* %a, i32 1 %1 = load i32* %arrayidx1, align 4, !tbaa !1 %add = add nsw i32 %1, %0 %arrayidx2 = getelementptr inbounds i32* %a, i32 2 %2 = load i32* %arrayidx2, align 4, !tbaa !1 %add3 = add nsw i32 %add, %2 %arrayidx4 = getelementptr inbounds i32* %a, i32 3 %3 = load i32* %arrayidx4, align 4, !tbaa !1 %add5 = add nsw i32 %add3, %3 %arrayidx6 = getelementptr inbounds i32* %a, i32 4 %4 = load i32* %arrayidx6, align 4, !tbaa !1 %add7 = add nsw i32 %add5, %4 %arrayidx8...

...idx, align 8 %vecinit = insertelement <4 x double> undef, double %0, i32 0 %add = add i64 %i, 1 %arrayidx1 = getelementptr inbounds double, double* %ptr, i64 %add %1 = load double, double* %arrayidx1, align 8 %vecinit2 = insertelement <4 x double> %vecinit, double %1, i32 1 %add3 = add i64 %i, 2 %arrayidx4 = getelementptr inbounds double, double* %ptr, i64 %add3 %2 = load double, double* %arrayidx4, align 8 %vecinit5 = insertelement <4 x double> %vecinit2, double %2, i32 2 %add6 = add i64 %i, 3 %arrayidx7 = getelementptr inbounds double, double* %ptr, i64 %a...

...pture readonly %a, i32 %n) #0 {entry: %0 = load i32* %a, align 4, !tbaa !1 %arrayidx1 = getelementptr inbounds i32* %a, i32 1 %1 = load i32* %arrayidx1, align 4, !tbaa !1 %add = add nsw i32 %1, %0 %arrayidx2 = getelementptr inbounds i32* %a, i32 2 %2 = load i32* %arrayidx2, align 4, !tbaa !1 %add3 = add nsw i32 %add, %2 %arrayidx4 = getelementptr inbounds i32* %a, i32 3 %3 = load i32* %arrayidx4, align 4, !tbaa !1 %add5 = add nsw i32 %add3, %3 %arrayidx6 = getelementptr inbounds i32* %a, i32 4 %4 = load i32* %arrayidx6, align 4, !tbaa !1 %add7 = add nsw i32 %add5, %4 %arrayidx8 = getel...

..., double* %element33 %mul1 = fmul fast double %load20, %load10 %mul2 = fmul fast double %load21, %load11 %mul3 = fmul fast double %load22, %load10 %mul4 = fmul fast double %load23, %load11 %add1 = fadd fast double %load30, %mul1 %add2 = fadd fast double %load31, %mul2 %add3 = fadd fast double %load32, %mul3 %add4 = fadd fast double %load33, %mul4 %out0 = getelementptr inbounds double, double* %out, i32 0 %out1 = getelementptr inbounds double, double* %out, i32 1 %out2 = getelementptr inbounds double, double* %out, i32 2 %out3 = getelementptr inbou...

...+inf] %s.02 = phi i32 [ 0, %entry ], [ %add2, %for.body ] [0, +inf] %j.01 = phi i32 [ 0, %entry ], [ %add1, %for.body ] [0, +inf] %add = add nsw i32 %j.01, %i.03 [1, +inf] %add1 = add nsw i32 %add, 1 [1, +inf] %add2 = add nsw i32 %s.02, %add1 [1, +inf] %inc = add nsw i32 %i.03, 1 [2, +inf] %add3 = add nsw i32 %add2, %add1 -- Davide

...ayidx1 = getelementptr inbounds i32* %a, i32 1 > > > %1 = load i32* %arrayidx1, align 4, !tbaa !1 > > > %add = add nsw i32 %1, %0 > > > %arrayidx2 = getelementptr inbounds i32* %a, i32 2 > > > %2 = load i32* %arrayidx2, align 4, !tbaa !1 > > > %add3 = add nsw i32 %add, %2 > > > %arrayidx4 = getelementptr inbounds i32* %a, i32 3 > > > %3 = load i32* %arrayidx4, align 4, !tbaa !1 > > > %add5 = add nsw i32 %add3, %3 > > > %arrayidx6 = getelementptr inbounds i32* %a, i32 4 > > > %4 = load i32*...

...uble> undef, double %0, i32 0 >> %add = add i64 %i, 1 >> %arrayidx1 = getelementptr inbounds double, double* %ptr, i64 %add >> %1 = load double, double* %arrayidx1, align 8 >> %vecinit2 = insertelement <4 x double> %vecinit, double %1, i32 1 >> %add3 = add i64 %i, 2 >> %arrayidx4 = getelementptr inbounds double, double* %ptr, i64 %add3 >> %2 = load double, double* %arrayidx4, align 8 >> %vecinit5 = insertelement <4 x double> %vecinit2, double %2, i32 2 >> %add6 = add i64 %i, 3 >> %arrayidx7 = g...