search for: orizon

Dear All, I have tested a few examples of LLVM-JIT Framework on Linux x86 Machine. So generating functions on the fly and then executing them is OK on linux i.e. i686-pc-linux-gnu My question is: Can we use the LLVM-JIT on a baremetal x86 machine ? Actually my target is a virtual machine, and I need some dynamic code generation support. I intend to use LLVM-JIT (if possible) for this

Hi Mian, Looking at the runlog, everything seems fine until LLVM attempts to use lseek() on a file. You see the PANIC because Horizon hasn't implemented lseek yet. Obviously the version of GlibC I was using does not use lseek in that circumstance, but yours does. You just need to implement lseek :) Cheers, James -----Original Message----- From: Mian M. Hamayun [mailto:mian-muhammad.hamayun at imag.fr] Sent: 03 November 20...

...mp;modl; Is this 'module' somehow related to 'KERNEL_HBC' that we specified earlier ? If yes then how I am getting the size of this special file to be zero, whereas the size of my 'hello_world.hbc' is 225 bytes. If no, then what is it ? Secondly You have mentioned on the Horizon wiki: "The build process will produce a version of horizon statically linked with code that provides enough of a UNIX environment for LLVM and libstdc++ to function" Could you please shed some more light on this aspect (Some links, if possible), on how you have accomplished this ? I a...

Hi, First question: "/module" is mapped to a special file that reads a kernel module passed in by the bootloader. Much like GRUB, kiwi's bootloader loads a kernel and can load one or more extra files into memory. These are passed to the kernel. The horizon kernel expects one file, which it makes accessible at "/module". This should be set up to be whatever you set KERNEL_HBC to be. Second question: The program is statically compiled on the host system against the host C and C++ libraries. Then, it is patched slightly to change linux syscal...