search for: keywoard

...*restrict M, int *restrict*restrict L) { S1: M[1][1] = 1; S2: L[2][2] = 2; } When I iterate over MemoryDependenceAnalysis on the S2 statement, I get the load instruction for the first depth of the array, that’s ok. But I get also the load and store for the S1 statement. I assume the restrict keywoard help the alias analysis to found that pointers don’t alias. The prototype of this function in llvm-ir is: define void @fct(i32** noalias %M, i32** noalias %L) #0 { …. Did this noalias attribute say that both pointer of i32** didn’t alias? Also, when I check wich AliasAnalysis pass is called with...

...gt;> S2: L[2][2] = 2; >> } >> >> When I iterate over MemoryDependenceAnalysis on the S2 statement, I get >> the load instruction for the first depth of the array, that’s ok. But I get >> also the load and store for the S1 statement. >> I assume the restrict keywoard help the alias analysis to found that >> pointers don’t alias. >> The prototype of this function in llvm-ir is: >> define void @fct(i32** noalias %M, i32** noalias %L) #0 { …. >> >> Did this noalias attribute say that both pointer of i32** didn’t alias? >> >&g...

I forgot that lli was "special". It uses the "JIT" keywoard which means "figure out the right libraries to use for a JIT compiler and runtime". So, just add this, to tools/lli/Makefile: USEDLIBS := LLVMBCWriter That worked for me. Reid. On Thu, 2005-02-24 at 16:58, Patrick Meredith wrote: > Where do I add that line? Just putting it in th...

Are you suggesting that we have "always_inline" and "never_inline" keywoards that can be attributed to functions? If so, why do you want this level of control? What's wrong with the current inlining pass? Reid. On Sat, 2005-05-07 at 20:34 +0200, Markus F.X.J. Oberhumer wrote: > As I've just seen that there are some things going on w.r.t the long > needed i...

Where do I add that line? Just putting it in the vanilla Makefile in tools/lli doesn't work. ----- Original Message ----- From: "Reid Spencer" <reid at x10sys.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Thursday, February 24, 2005 6:50 PM Subject: Re: [LLVMdev]Linker error building (modified) lli >

Hi Patrick, You need to modify your makefile for building your version of lli so that it includes the LLVMBCWriter.o library. You can do this with a line like: LLVM_LIBS=LLVMBCWriter if you're using the LLVM Makefile system. Otherwise you just need to make sure that {Debug,Release}/lib/LLVMBCWriter.o gets added to the link line. Reid. On Thu, 2005-02-24 at 16:37, Patrick Meredith wrote: