search for: tji

...bac2d in llvm::FunctionPassManagerImpl::doInitialization (this=0x53934c0, M=@0x1902d20) at PassManager.cpp:1111 #8 0x006b4ecb in llvm::FunctionPassManager::doInitialization (this=0x5395724) at PassManager.cpp:1094 #9 0x0036f6a8 in llvm::JIT::JIT (this=0x53956b0, MP=0x5395170, tm=@0x21ec400, tji=@0x21ec588, JMM=0x0) at JIT.cpp:101 #10 0x0036f6e9 in llvm::JIT::JIT (this=0x53956b0, MP=0x5395170, tm=@0x21ec400, tji=@0x21ec588, JMM=0x0) at JIT.cpp:102 #11 0x00375971 in llvm::JIT::createJIT (MP=0x5395170, ErrorStr=0x0, JMM=0x0) at TargetSelect.cpp:75 #12 0x0037667e in llvm::JIT::create (MP=...

...achine, then sending it to another to > be executed, and references from one buffer to another won't work in > that environment.  So that model needs to continue to work.  If you > want to generalize it so other models work as well, go ahead. Maybe what I should do then is change TargetJITInfo::allocateSeparateGVMemory to allocateGVsWithCode and invert the meaning, since I feel like most users probably just want malloc or something similar. You could then subclass the appropriate TJI class and override that method. Would that be a reasonable API change? No one else calls or overr...

...another to >> be executed, and references from one buffer to another won't work in >> that environment.  So that model needs to continue to work.  If you >> want to generalize it so other models work as well, go ahead. > > Maybe what I should do then is change > TargetJITInfo::allocateSeparateGVMemory to allocateGVsWithCode and > invert the meaning, since I feel like most users probably just want > malloc or something similar.  You could then subclass the appropriate > TJI class and override that method.  Would that be a reasonable API > change?  No one...

...e not thread safe Both of these classes have additional members which I have not protected. It looked to my brief analysis that they were used in a read-only fashion. Can anyone tell me if I am wrong: ExecutionEngine: Module &CurMod; const TargetData *TD; JIT: TargetMachine &TM; TargetJITInfo &TJI; MachineCodeEmitter *MCE; I specifically did not protect the ExecutionEngine::CurMod member because a reference is returned via ExecutionEngine::getModule(). If access to it must be serialized, it must be done very carefully. I tried to make getModule return a constant reference,...

On Jun 29, 2009, at 5:41 PMPDT, Reid Kleckner wrote: > So I (think I) found a bug in the JIT: > http://llvm.org/bugs/show_bug.cgi?id=4483 > > Basically, globals used by a function are allocated in the same buffer > as the first code that uses it. However, when you free the machine > code, you also free the memory holding the global's data. The address > is still in the

So I (think I) found a bug in the JIT: http://llvm.org/bugs/show_bug.cgi?id=4483 Basically, globals used by a function are allocated in the same buffer as the first code that uses it. However, when you free the machine code, you also free the memory holding the global's data. The address is still in the GlobalValue map, so any other code using that global will access freed memory, which

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

...7ZZ}gK^!G* zB_70l(4tx9YxU<JrThZaNty>TleAB9of>B)E6Fq}3o%d02nz10Q at gbE_lr-{-K_t^ zG30(SFCw}n3ud(8Vc!5c<=O*x(|b{&hi6YTT_kWb<t2(NH4M7xI;$-L)Q6L#ej(1d z2BjsXRdb?>hc;0`E~PLN%AU}31UI4TIAs%u9^L*r=<+f~-=S*b982ylv(j$5YQ==Q z`&86T1~~?4xJ&5*FvlK9_x;DjfwtrJ^s~dKa(alIkCLE})RV6u+tJIOb9Ue^-tajP z6gmfVuI2`7NHoOVjx1b>&T{UUH_}nTN2_glh#xty^eUv03$sQ1xFlsm0kbE#9cd+e z#nq<->6{oGgI-wusj=;5L-^qd*=UqL;yPqqD at t;P=vgi(qI(!9_-v8+=w->Ki!`!I zn at E#6cC|-_Z7OXd_+_P`c258Yy2*&|(gtOT)ty#LI4=`+qH4QzIdD^r+U_Z2`?E9d zQKDhc2bHg&3B{V9^%;LcT^VW=GW5oELtdWrp3g`T=Cc at _Qkd*)%40...