search for: walksub

Displaying 6 results from an estimated 6 matches for "walksub".

Did you mean: walks
2011 Mar 02
3
[LLVMdev] Compile C files to one .bc file
...ot;bh" C program from the Olden benchmark to one bc file. # compile source files into an LLVM bitcode file llvm-gcc -emit-llvm -c args.c -o args.bc -w -DTORONTO llvm-gcc -emit-llvm -c newbh.c -o newbh.bc -w -DTORONTO llvm-gcc -emit-llvm -c util.c -o util.bc -w -DTORONTO llvm-gcc -emit-llvm -c walksub.c -o walksub.bc -w -DTORONTO # To link files together using llvm-ld llvm-ld -o bh.bc newbh.bc args.bc util.bc walksub.bc -lm But when I try to run my pass over bh.bc file or just compile it to native code llc bh.bc -o bh.s I get the following error. llc: bh.bc:1:1: error: expected top-level enti...
2010 Apr 27
2
[LLVMdev] Setting alignment for a ByVal argument
Hi, Thanks for the help. I tried this out, but on x86_64 and with llvm 2.6 and llvm-gcc 4.2.1, I dont seem to get an aligned variable. This is the function definition that I have define internal fastcc void @walksub(%struct.hgstruct* noalias nocapture sret %agg.result, %struct.node* %p, double %dsq, %struct.hgstruct* byval align 64 %hg, i32 %level) nounwind { And these are the call sites, call fastcc void @walksub(%struct.hgstruct* noalias sret %2, %struct.node* %tmp399, double %tmp398, %struct.hgstruct* byv...
2010 Apr 27
0
[LLVMdev] Setting alignment for a ByVal argument
Hi Arushi, > If I want a particular alignment on a ByVal argument, should I specify > it as a function attribute, or should I also add the attribute to > every callsite that calls that function. in theory you should do both. For example, if the call is an indirect call (i.e. to a function pointer where the function is not known) then it should be clear that you need to put the
2010 Apr 26
2
[LLVMdev] Setting alignment for a ByVal argument
Hi, If I want a particular alignment on a ByVal argument, should I specify it as a function attribute, or should I also add the attribute to every callsite that calls that function. Thanks, Arushi
2014 Jan 28
3
[LLVMdev] MergeFunctions: reduce complexity to O(log(N))
Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability
2014 Jan 30
3
[LLVMdev] MergeFunctions: reduce complexity to O(log(N))
...la.ll 5 9414 0 0.01 9405 0 0.01 9405 vlalloc.ll 3 15326 0 0.01 15292 0 0.01 15292 vlc.ll 33 148671 0 0.02 148650 0 0.02 142630 vl_comp.ll 2 15625 0 0.01 15591 0 0.01 15591 volume.ll 1 4513 0 0.01 4488 0 0.01 4488 vor.ll 12 87187 0 0.02 87165 0 0.02 87165 vprobes.ll 2 94612 0 0.01 94579 0 0.01 94579 walksub.ll 1 7504 0 0.01 7486 0 0.01 7486 warshall.ll 2 9631 0 0.01 9605 0 0.01 9605 watesides.ll 1 20153 0 0.01 20120 0 0.01 20120 wc.ll 21 30760 0 0.01 30735 0 0.01 30735 weighted_prediction.ll 8 238338 0 0.03 238317 0 0.02 238317 whetstone.ll 6 48962 0 0.01 48947 0 0.02 48947 Wildcard.ll 43 294055 0 0.0...