search for: jittests

...CallBug.ll LLVM :: ExecutionEngine/hello.ll LLVM :: ExecutionEngine/hello2.ll LLVM :: ExecutionEngine/stubs.ll LLVM :: ExecutionEngine/test-call.ll LLVM :: ExecutionEngine/test-fp.ll LLVM :: ExecutionEngine/test-loadstore.ll LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JIT.GlobalInFunction LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.EscapedLazyStubStillCallable LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.FarCallT...

...-complete.c Clang :: Index/crash-recovery-reparse.c Clang :: Index/crash-recovery.c LLVM :: BugPoint/crash-narrowfunctiontest.ll LLVM :: BugPoint/metadata.ll LLVM :: BugPoint/remove_arguments_test.ll LLVM :: Feature/load_module.ll LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyFunctionIsntCompiled LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/LazyLoadedJITTest.MaterializableAvailableExternallyFunctionIsntCompiled Expected Passes : 81...

...ionEngine/hello.ll >    LLVM :: ExecutionEngine/hello2.ll >    LLVM :: ExecutionEngine/stubs.ll >    LLVM :: ExecutionEngine/test-call.ll >    LLVM :: ExecutionEngine/test-fp.ll >    LLVM :: ExecutionEngine/test-loadstore.ll >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/JIT.GlobalInFunction >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.EscapedLazyStubStillCallable >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Assert...

...nfs_home/chenwj/test/native-build/arm2/Debug+Asserts/bin/lli' '/nfs_home/chenwj/test/llvm/test/ExecutionEngine/test-malloc.ll' > '/dev/null' -- ******************** Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90. FAIL: LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.AvailableExternallyFunctionIsntCompiled (5865 of 6030) ******************** TEST 'LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.AvailableExternallyFunctionIsntCompiled' FAILED ******************** Note: Google Test filter = JITTest.AvailableExternallyFunctionIsntCo...

...le.ll Error opening '/home/emeewis/build/llvm-release-clang-cmake/lib/./BugpointPasses.so': /home/emeewis/build/llvm-release-clang-cmake/lib/./BugpointPasses.so: Undefined symbol "_ZNK4llvm4Pass11getPassNameEv" -load request ignored. LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyFunctionIsntCompiled LLVM ERROR: Program used external function 'JITTest_AvailableExternallyFunction' which could not be resolved! LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted LLVM ERROR: Could not resolve ext...

...   LLVM :: ExecutionEngine/hello2.ll >>    LLVM :: ExecutionEngine/stubs.ll >>    LLVM :: ExecutionEngine/test-call.ll >>    LLVM :: ExecutionEngine/test-fp.ll >>    LLVM :: ExecutionEngine/test-loadstore.ll >>    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/JIT.GlobalInFunction >>    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted >>    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.EscapedLazyStubStillCallable >>    LLVM-Unit :: >> Executio...

...Time: 2136.45s ******************** Failing Tests (7): LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll LLVM :: ExecutionEngine/test-fp.ll LLVM :: Object/objdump-disassembly-inline-relocations.test LLVM :: Object/objdump-trivial-object.test LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JIT.GlobalInFunction LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.FunctionPointersOutliveTheirCreator Expected Passes : 3239 Expected Failures : 46 Unsupported Tests : 235...

Hi, I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on Windows 7 using MinGW. From there, I thought I would run the tests located under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass without any problem, except for JITTests which fails on the MultiJitTest.JitPool test: [==========] Running 25 tests from 6 test cases. [----------] Global test environment set-up. [----------] 3 tests from MultiJitTest [ RUN...

Hi all, I'm compiling current SVN HEAD on Linux/x86. The tests are failing on PowerPC due to the following assertion failure : JITTests: PPCCodeEmitter.cpp:152: unsigned int<unnamed>::PPCCodeEmitter:: getMachineOpValue(const llvm::MachineInstr&, const llvm::MachineOperand&) const: Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed. Is anyone working on the PowerPC backend?...

2011/11/18 Alan Garny <alan.garny at dpag.ox.ac.uk>: > I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on > Windows 7 using MinGW. From there, I thought I would run the tests located > under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, > JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass > without any problem, except for JITTests which fails on the > MultiJitTest.JitPool test: > [ RUN      ] MultiJitTest.JitPool > > MultiJITTest.cpp:164: Failure > > Value of: (intptr_t)&getPointerToNamedFunction...

Hello, I asked here for kind of reference GCC version which LLVM development team is using for *native* testing on ARM hardware. (no cross compilation!) last week or so. I've been curious myself how the situation looks and so I tested LLVM 2.9 as a reference point and LLVM HEAD as of June 29 on ARMv7 (two boards with two different Ubuntu versions) compiled by GCC 4.3.4, 4.4.1, 4.4.5,

Erik de Castro Lopo <mle+cl <at> mega-nerd.com> writes: > > Hi all, > > I'm compiling current SVN HEAD on Linux/x86. The tests are failing > on PowerPC due to the following assertion failure : > > JITTests: PPCCodeEmitter.cpp:152: unsigned int<unnamed>::PPCCodeEmitter:: > getMachineOpValue(const llvm::MachineInstr&, const llvm::MachineOperand&) > const: Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed. > > Is anyone working on...

Pinging again, more loudly :-) Michael Muller wrote: > > Ping. (looking for someone to review or commit this, thanks) > > Michael Muller wrote: > > > > Thanks, Duncan - > > > > > Hi Michael, > > > > > > > --- lib/ExecutionEngine/JIT/JITEmitter.cpp (revision 163478) > > > > +++ lib/ExecutionEngine/JIT/JITEmitter.cpp

On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote: > > Hi, I found a bug in the code that generates exception tables, I've attached > what I think is the correct fix. > > When you run out of space writing to a buffer, the buffer management code > simply stops writing at the end of the buffer. It is the responsibility of > the caller to

Eric Christopher wrote: > > On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote: > > > > > Hi, I found a bug in the code that generates exception tables, I've attached > > what I think is the correct fix. > > > > When you run out of space writing to a buffer, the buffer management code > > simply stops writing at the

On Tue, Dec 8, 2009 at 1:05 AM, Albert Graef <Dr.Graef at t-online.de> wrote: > Nick Lewycky wrote: >> Can you prepare a standalone testcase that demonstrates the problem? See >> unittests/ExecutionEngine/JIT/*.cpp to get your started. > > Probably. I'd essentially have to replicate some minimal runtime > environment and IR as created by the Pure interpreter.

Jeffrey Yasskin wrote: > Not really. I need to find the IR it's compiling into bad code, and > `make check` doesn't give me the command lines so I can gdb them. It's > also going to be tricky for me, who's not familiar with your > implementation, to find which function is crashing and where it's > compiled. Either a patch to JITTest.cpp or an IR file+an lli

On Tue, Dec 22, 2009 at 6:14 AM, Chris Lattner <clattner at apple.com> wrote: > On Dec 19, 2009, at 3:36 PM, Gianluca Guida wrote: >> Attached patch makes runJITOnFunction more reliable. > > When would MCI be null? Everytime you call recompileAndRelinkFunction. It calls runJITOnFunction without specifying the MCI argument, which get defaulted to NULL. Gianluca -- It was a

Please add a test to http://llvm.org/viewvc/llvm-project/llvm/trunk/unittests/ExecutionEngine/JIT/JITTest.cpp?view=markup verifying that recompileAndRelinkFunction() keeps working. Then this fix will look fine to me. On Tue, Dec 22, 2009 at 12:23 AM, Gianluca Guida <glguida at gmail.com> wrote: > On Tue, Dec 22, 2009 at 6:14 AM, Chris Lattner <clattner at apple.com> wrote: >>

On Tue, Dec 22, 2009 at 5:51 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Please add a test to > http://llvm.org/viewvc/llvm-project/llvm/trunk/unittests/ExecutionEngine/JIT/JITTest.cpp?view=markup > verifying that recompileAndRelinkFunction() keeps working. Then this > fix will look fine to me. Here it is. Unfortunately I'm not exactly a C++ guy so I'm open to