similar to: [LLVMdev] Question about insert function or instruction.

Displaying 20 results from an estimated 600 matches similar to: "[LLVMdev] Question about insert function or instruction."

2004 May 21
1
[LLVMdev] Re: LLVMdev digest, Vol 1 #292 - 4 msgs
Hi, Thank Brian Gaeke so much. Following TraceBasicBlocks.cpp, I modified the code as below and could insert instruction or function I need into anywhere in Module. But it works well without BB->getInstList().push_back(InstrCall), and if I add the BB->getInstList().push_back() following new CallInst(), I got error information when runing opt. What is the reason for it? And is it necessary
2004 May 19
0
[LLVMdev] Question about insert function or instruction.
> What I want to do is to insert a call funcation into each basic > block, which is for statistic some information. I recommend that you look at the various pieces of code under llvm/lib/Transforms/Instrumentation, e.g. BlockProfiling.cpp and TraceBasicBlocks.cpp. They do essentially the same thing as you are trying to do. > 1) I implement call function in another c/cpp file and >
2005 Jan 28
2
[LLVMdev] Compiling errors for tracelib.c
Hi, Is there something wrong with my llvm-gcc compiler?: ------------------------ GNU C version 3.4-llvm 20030924 (experimental) (mingw32) compiled by GNU C version 3.4.1 (mingw special). GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 c:/projects/src/llvm-4/llvm/runtime/libtrace/tracelib.c:54: error: syntax error before "PRIMES"
2005 Jan 28
0
[LLVMdev] Compiling errors for tracelib.c
On Fri, 28 Jan 2005, Henrik Bach wrote: > Is there something wrong with my llvm-gcc compiler?: > c:/projects/src/llvm-4/llvm/runtime/libtrace/tracelib.c:54: warning: type > defaults to `int' in declaration of `PRIMES' > c:/projects/src/llvm-4/llvm/runtime/libtrace/tracelib.c:56: warning: data > definition has no type or storage class It looks like that file had
2009 Oct 20
2
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:
2009 Oct 20
3
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM
2009 Aug 28
1
[LLVMdev] [Cygwin] 'make install' woes
I am getting the following on 'make install' on Cygwin both on debug and release builds :- llvm[3]: Installing Release /home/ang/llvm-coff/bin/llvmc.exe make[3]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc/driver' make[2]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc' make[1]: Leaving directory `/home/ang/build/llvm-coff/tools' make[1]: Entering
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In
2004 Dec 04
1
[LLVMdev] Question about writing a pass
Hi , I got a few for writing a pass. 1) Is it possible to use input parameters in command line ? For example, we got our own pass, ie. HELLO opt -load ../../Debug/lib/libHELLO.so -HELLO < hello.bc From the above command line, could we use some input parameter and we can read those parameter in Pass routine? 2) For splitting BB, the way what I did is to pick up instruction
2004 Apr 30
2
[LLVMdev] LLVM benchmarks against GCC
> > yesterday I got new SuSE 9.1 DVD, so i am going to enter this > > river again. Perhaps, this time all will be fine. > > Sounds great, please let me know how it goes. SuSE 9.1 is running OK. after 30 minute of compilation i get first errors: ********************* make[2]: Leaving directory `/pool/tmp/llvm/runtime/libtrace' make[2]: Entering directory
2004 Jul 21
0
[LLVMdev] GC questions.
Ok, that makes sense :). , Tobias On Wed, 21 Jul 2004, Chris Lattner wrote: > On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > > return *FieldPtr; > > > } > > > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > > cases? > > For the field pointer, one
2005 Jul 27
1
[LLVMdev] Help regarding profiling information
Hi, I am trying to obtain basic block profiles for mediabench g721 benchmark. I have successfully built llvm in profile_enabling mode. Then so as to find out the block execution frequency, I ran the command, analyze encode.out-cbe. It generated gmon.out which I read using gprof. However, I did not get the basic block level execution frequency. Can anybody help me as to how I can extract the basic
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > return *FieldPtr; > > } > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > cases? For the field pointer, one could use the getelementptr instruction: %pairty = { sbyte, sbyte, int* } %pairPtr = ... %fieldptr = getelementptr
2009 Sep 01
1
[LLVMdev] Problem building libprofile.
Hi, when I try to build libprofile with r80670 (both llvm and llvm-gcc) I get this error: make[1]: Entering directory `.../llvm-svn-debug-obj/runtime/libprofile' llvm[1]: Building Debug Bytecode Archive libprofile_rt.bca (internalize) llvm[1]: Installing Debug Shared Library /nfs/a5/astifter/astifter/llvm/llvm-svn-debug-obj/../llvm-svn-debug-install/lib/libprofile_rt.so 0 llvm-ld
2004 Apr 30
0
[LLVMdev] LLVM benchmarks against GCC
On Fri, 30 Apr 2004, [koi8-r] "Valery A.Khamenya[koi8-r] " wrote: > > The nightly tester is used for two purposes: making sure that nothing > > breaks (the unit tests) and keeping tabs on how well performance is doing > > (the spec and most multisource tests). It's not a reliable way to do > > serious benchmarking, but can give good insights into where
2013 Jun 23
1
2SLS / TSLS / SEM non-linear
Dear all, I try to conduct a SEM / two stage least squares regression with the following equations: First: X ~ IV1 + IV2 * Y Second: Y ~ a + b X therein, IV1 and IV2 are the two instruments I would like to use. the structure I would like to maintain as the model is derived from economic theory. My problem here is that I have trouble solving the equations to get the reduced form so I can run
2012 Jul 29
1
Mesa build issue... is it just me?
Anyone else getting this when building the latest mesa? make[3]: Entering directory `/usr/local/nouveau/mesa2/mesa/src/gallium/targets/dri-nouveau' gcc -c -I. -I../../../../src/mesa/drivers/dri/common -Iserver -I../../../../include -I../../../../include/GL/internal -I../../../../src/mapi -I../../../../src/gallium/include -I../../../../src/gallium/auxiliary