search for: orcmcjit

...ExecutionEngine/MCJIT/remote/test-global-init-nonzero-remote.ll LLVM :: ExecutionEngine/MCJIT/remote/test-global-init-nonzero-sm-pic.ll LLVM :: ExecutionEngine/MCJIT/remote/test-ptr-reloc-remote.ll LLVM :: ExecutionEngine/MCJIT/remote/test-ptr-reloc-sm-pic.ll LLVM :: ExecutionEngine/OrcMCJIT/remote/cross-module-a.ll LLVM :: ExecutionEngine/OrcMCJIT/remote/eh.ll LLVM :: ExecutionEngine/OrcMCJIT/remote/multi-module-a.ll LLVM :: ExecutionEngine/OrcMCJIT/remote/simpletest-remote.ll LLVM :: ExecutionEngine/OrcMCJIT/remote/stubs-remote.ll LLVM :: ExecutionEngine/OrcMCJIT/...

...". Failing Tests (10): LLVM :: ExecutionEngine/MCJIT/eh-lg-pic.ll LLVM :: ExecutionEngine/MCJIT/eh-sm-pic.ll LLVM :: ExecutionEngine/MCJIT/eh.ll LLVM :: ExecutionEngine/MCJIT/multi-module-eh-a.ll LLVM :: ExecutionEngine/MCJIT/remote/eh.ll LLVM :: ExecutionEngine/OrcMCJIT/eh-lg-pic.ll LLVM :: ExecutionEngine/OrcMCJIT/eh-sm-pic.ll LLVM :: ExecutionEngine/OrcMCJIT/eh.ll LLVM :: ExecutionEngine/OrcMCJIT/multi-module-eh-a.ll LLVM :: ExecutionEngine/OrcMCJIT/remote/eh.ll -Krzysztof -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Fo...

Hi, I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in -rc1 before I could send out a release announcement, so I decided to merge the fix and tag -rc2 to save some testing cycles. We can always use more testers, so if you are interested in helping, let me know. Thanks, Tom

...ecutionEngine/MCJIT/eh-lg-pic.ll > LLVM :: ExecutionEngine/MCJIT/eh-sm-pic.ll > LLVM :: ExecutionEngine/MCJIT/eh.ll > LLVM :: ExecutionEngine/MCJIT/multi-module-eh-a.ll > LLVM :: ExecutionEngine/MCJIT/remote/eh.ll > LLVM :: ExecutionEngine/OrcMCJIT/eh-lg-pic.ll > LLVM :: ExecutionEngine/OrcMCJIT/eh-sm-pic.ll > LLVM :: ExecutionEngine/OrcMCJIT/eh.ll > LLVM :: ExecutionEngine/OrcMCJIT/multi-module-eh-a.ll > LLVM :: ExecutionEngine/OrcMCJIT/remote/eh.ll > > > -Krzysztof > > >...

Hello everyone, 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3 Binaries will be added as they become available. There are currently no open release blockers, which means if nothing new comes up, the final release could ship soon and this is

...ecutionEngine/RuntimeDyld/Targets/RuntimeDyldCOFFI386.h to see if the relocation is getting applied correctly in the context of your JIT? You may be able to repro this more easily using `lli`. It has a `-jit-kind` argument that should get you into the JIT codepath. (see test/ExecutionEngine/{MCJIT,ORCMCJIT}/) -- Sean Silva On Tue, Jun 6, 2017 at 1:09 AM, Nikodemus Siivola < nikodemus at random-state.net> wrote: > This is on Windows 10: didn't yet manage to get a 64-bit toolchain set up > that agreed on everything necessary. > > Dumped bitcode, but when I did that everything...

...dCOFFI386.h to see if the relocation is getting >> applied correctly in the context of your JIT? >> >> You may be able to repro this more easily using `lli`. It has a >> `-jit-kind` argument that should get you into the JIT codepath. (see >> test/ExecutionEngine/{MCJIT,ORCMCJIT}/) >> >> -- Sean Silva >> >> >> On Tue, Jun 6, 2017 at 1:09 AM, Nikodemus Siivola < >> nikodemus at random-state.net> wrote: >> >>> This is on Windows 10: didn't yet manage to get a 64-bit toolchain set >>> up that agreed on ever...

On Mon, Jun 5, 2017 at 1:34 PM, Nikodemus Siivola < nikodemus at random-state.net> wrote: > Uh. Turns out that if I hide the pointer to @foo from LLVM by passing it > through an opaque identity function ... then everything works fine. > > Is this a bug in LLVM or is there some magic involving globals I'm > misunderstanding? > This looks like a bug in the handling of

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom

Hello everyone, 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc6. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc6 This is the same as rc5 plus one very minor change (r371969) that still seemed good to pick up. I'm not allocating extra time for testing this one, expecting to tag