search for: unitest

Displaying 5 results from an estimated 5 matches for "unitest".

Did you mean: unittest
2012 Oct 13
2
[LLVMdev] Dynamically loading native code generated from LLVM IR
Daniel, I didn't find the MCJIT directory under unitests/ExecutionEngine ... there is only a directory called JIT. You mean this directory ? Many thanks --Armin Malea, Daniel wrote: > Take a look at the MCJIT unit tests under unittests/ExecutionEngine/MCJIT > > The MCJITTestBase class does the majority of the interactions with the LLVM AP...
2012 Oct 13
0
[LLVMdev] Dynamically loading native code generated from LLVM IR
It's definitely there. It was added in r165246 recently so you probably have an older version. Amara On 13 October 2012 23:02, Armin Steinhoff <as at steinhoff-automation.com> wrote: > Daniel, > > I didn't find the MCJIT directory under unitests/ExecutionEngine ... there > is only a directory called JIT. > You mean this directory ? > > Many thanks > > --Armin > > > > > Malea, Daniel wrote: >> >> Take a look at the MCJIT unit tests under unittests/ExecutionEngine/MCJIT >> >> The MCJI...
2012 Oct 13
0
[LLVMdev] Dynamically loading native code generated from LLVM IR
Take a look at the MCJIT unit tests under unittests/ExecutionEngine/MCJIT The MCJITTestBase class does the majority of the interactions with the LLVM API you're referring to. Good luck, Dan On 2012-10-13, at 4:57 AM, "Armin Steinhoff" <as at steinhoff-automation.com> wrote: > > Kaylor, > > do you have some good documented example code which shows the usage of
2012 Oct 13
2
[LLVMdev] Dynamically loading native code generated from LLVM IR
Kaylor, do you have some good documented example code which shows the usage of the MCJIT ? This would help a lot ... the sematic of lots of API calls are not intuitively understandable. Best Regards --Armin Kaylor, Andrew wrote: > I'm not sure I understand your use case, but MCJIT (as opposed to the legacy JIT) does almost exactly what you're asking for. It generates an
2017 Mar 27
5
4.0.1 Release Schedule + Need feedback for improving stable releases
Hi, I would like to start a discussion about improvements to the stable release process, but first, here is a proposed schedule for the 4.0.1 release. May 1, 2017 -rc1 May 22, 2017 Deadline for submitting merge request May 29, 2017 Deadline for merging changes. June 3, 2017 -rc2 June 10, 2017 Final Release This is slightly different from previous stable releases in that we are doing an early