search for: zagorowicz

...at triggers this bug, or is this something you discovered just by reading the code? Cheers, Lang. On Thu, Nov 13, 2014 at 8:46 AM, David Blaikie <dblaikie at gmail.com> wrote: > [+Lang, owner of JITs, defender of register allocators, etc] > > On Thu, Nov 13, 2014 at 8:29 AM, Radek Zagorowicz < > radek.zagorowicz at gmail.com> wrote: > >> Hi all. >> >> I found some issue in implementation of finalizeObject function in >> MCJIT.cpp. If you look at the source code of the function, you can notice >> that machine code for second "owned" mo...

Hi all. I found some issue in implementation of finalizeObject function in MCJIT.cpp. If you look at the source code of the function, you can notice that machine code for second "owned" module will never be generated if it doesn't depend on the first one. More over it will cause a crash if entry point isn't in first module. Implementation of finalizeObject using for loop will

Hi guys. I found a little bug in implementation of MCJIT. I noticed that when I added object file (with all needed debug information) to lli by using -extra-object flag, it's impossible to debug it with gdb. Object file is in ELF format generated by llc. It is properly loaded by mcjit. I noticed that the reason is probably in lack of calling "registerWithDebugger()" after object