search for: jump_cal

...(), but didn't #include <stdlib.h>. The resulting code compiled without warning or error, but the resulting code was broken, due to the arguments not being seen as live, e.g.: Without #include <stdlib.h>: 0x181e8b0: i32 = TargetGlobalAddress <i32 (...)* @abs> 0 [TF=1] => JUMP_CALLi <ga:abs>[TF=1], %r2<imp-def>, %r3<imp-def>, %r4<imp-def,dead>, %r5<imp-def,dead>, %r6<imp-def,dead>, %r7<imp-def,dead>, %r8<imp-def,dead>, %r9<imp-def,dead>, %r10<imp-def,dead> With #include <stdlib.h>: 0x181e8b0: i32 = TargetGl...

Mark Muir wrote: > I've developed a working LLVM back-end (based on LLVM 2.6) for a custom architecture with its own tool chain. This tool chain creates stand-alone programs from a single assembly. We used to use GCC, which supported producing a single machine assembly from multiple source files. > > I modified Clang to accept the architecture, but discovered that clang-cc (or the

.... The resulting code > compiled without warning or error, but the resulting code was broken, due to > the arguments not being seen as live, e.g.: > > Without #include <stdlib.h>: > > 0x181e8b0: i32 = TargetGlobalAddress <i32 (...)* @abs> 0 [TF=1] > => JUMP_CALLi <ga:abs>[TF=1], %r2<imp-def>, %r3<imp-def>, > %r4<imp-def,dead>, %r5<imp-def,dead>, %r6<imp-def,dead>, %r7<imp-def,dead>, > %r8<imp-def,dead>, %r9<imp-def,dead>, %r10<imp-def,dead> > > With #include <stdlib.h>: > &gt...

I've developed a working LLVM back-end (based on LLVM 2.6) for a custom architecture with its own tool chain. This tool chain creates stand-alone programs from a single assembly. We used to use GCC, which supported producing a single machine assembly from multiple source files. I modified Clang to accept the architecture, but discovered that clang-cc (or the Clang Tool subclass inside Clang)