>Since MCJIT works on x86, please don't remove it from the supported >platforms list. One downside of using the macro trick is that the testnames>are still printed even when they are disabled. It sounds like you need to >modify the macro to also check for the target triple as well...This was just a temporary change to see how it works.>There isn't anything in MCJIT as far as I know that prevents crosscompilation.>That said, the SectionMemoryManager that's used by the unit tests doesn't >support remote execution. However, the RemoteMemoryManager has been >improving lately; it could foreseeably be used to add remote execution >support to the tests.That explains why MCJIT test executable (build/unittests/ExecutionEngine/MCJIT/MCJITTests) was an X86 binary in my case. It appears to me that these tests will always fail for cross-compilation unless modified for remote execution. I noticed "TARGET_HAS_JIT" flag in Makefile.config. Can I use this flag to exclude MCJIT and JIT tests when not set? This will be a simpler change than modifying the macro. Thanks, Jyotsna
On 2013-03-13 3:15 AM, "Jyotsna Verma" <jverma at codeaurora.org> wrote:> >I noticed "TARGET_HAS_JIT" flag in Makefile.config. Can I use this flag to >exclude MCJIT and JIT tests when not set? This will be a simpler change >than >modifying the macro. > >Thanks, >JyotsnaTARGET_HAS_JIT seems to be an autoconf thing (also, not really sure how it works) and has no equivalent in the cmake world. If you do want to use TARGET_HAS_JIT, please provide an equivalent for cmake users.
Will do that. Thanks! -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation>-----Original Message----- >From: Malea, Daniel [mailto:daniel.malea at intel.com] >Sent: Wednesday, March 13, 2013 3:31 PM >To: Jyotsna Verma; llvmdev at cs.uiuc.edu >Subject: Re: [LLVMdev] Disabling ExecutionEngine tests for Hexagon > > > >On 2013-03-13 3:15 AM, "Jyotsna Verma" <jverma at codeaurora.org> wrote: > >> >>I noticed "TARGET_HAS_JIT" flag in Makefile.config. Can I use this flag >>to exclude MCJIT and JIT tests when not set? This will be a simpler >>change than modifying the macro. >> >>Thanks, >>Jyotsna > > >TARGET_HAS_JIT seems to be an autoconf thing (also, not really sure how it >works) and has no equivalent in the cmake world. If you do want to use >TARGET_HAS_JIT, please provide an equivalent for cmake users.
Reasonably Related Threads
- [LLVMdev] Disabling ExecutionEngine tests for Hexagon
- [LLVMdev] Disabling ExecutionEngine tests for Hexagon
- [LLVMdev] Disabling ExecutionEngine tests for Hexagon
- [LLVMdev] Disabling ExecutionEngine tests for Hexagon
- [LLVMdev] TableGen related question for the Hexagon backend