search for: remotetargetextern

...nk addresses these issues. Can you try it out and see if it fixes this problem for you? If this doesn't do the trick, by stepping through the remote case in the debugger you can see what the communication is leading up to the failure. From there it should be relatively simple to use just the RemoteTargetExternal class to create a test driver that communicates with the child process in the same way. This ought to give you a failing test case completely independent of any of significant part of LLVM (unless the failure is entirely timing dependent). Thanks, Andy From: Renato Golin [mailto:renato.golin...

On 26 November 2013 19:05, Kaylor, Andrew <andrew.kaylor at intel.com> wrote: > I would also note that the failure isn’t actually in anything > MCJIT-specific. Aside from the fact that it seems to be clang-specific, > the code that is failing is specific to the lli remote implementation. > It’s not clear to me why it would fail under aggressive optimization with > clang,

...extract' llvm[2]: Compiling RemoteTarget.cpp for Release+Asserts build llvm[2]: Compiling Disassembler.cpp for Release+Asserts build make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/bugpoint' llvm[2]: Compiling BugDriver.cpp for Release+Asserts build llvm[2]: Compiling RemoteTargetExternal.cpp for Release+Asserts build llvm[2]: Compiling llvm-mc.cpp for Release+Asserts build llvm[2]: Compiling lli.cpp for Release+Asserts build llvm[2]: Compiling CrashDebugger.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable llvm-mc (without symbols) llvm[2]: ======= Finishe...