Displaying 3 results from an estimated 3 matches for "nollvm".
Did you mean:
gollvm
2008 Nov 24
0
[LLVMdev] how to track down a kernel miscompilation?
...g file for qemu/kvm with virtio
devices (I also think it will work with the default devices). The
build process uses llvm-gcc -> opt -> llc so you can add your own
(per-file) passes to the build process or debug specific passes.
Directories arch/x86/boot and arch/x86/boot/compressed specify NOLLVM
in their makefile which causes the make system to use gcc to build the
directory. options to opt are controlled by OPT_OPTIONS in the top
level makefile.
Some caviots and notes:
* This has only been tested in kvm and qemu and mostly only with
virtio net and block devices. Other configurations ar...
2008 Nov 24
1
[LLVMdev] how to track down a kernel miscompilation?
...virtio
> devices (I also think it will work with the default devices). The
> build process uses llvm-gcc -> opt -> llc so you can add your own
> (per-file) passes to the build process or debug specific passes.
>
> Directories arch/x86/boot and arch/x86/boot/compressed specify NOLLVM
> in their makefile which causes the make system to use gcc to build the
> directory. options to opt are controlled by OPT_OPTIONS in the top
> level makefile.
>
> Some caviots and notes:
> * This has only been tested in kvm and qemu and mostly only with
> virtio net and block...
2008 Nov 24
4
[LLVMdev] how to track down a kernel miscompilation?
Hi,
I am trying to build the Linux kernel with LLVM.
'ARCH=um' appears to work, now I am trying to get 'ARCH=x86' to work.
So far it seems there is something wrong with the boot vga code (it
finds no video modes), the acpi code, and the serial console code.
I am now trying to compile drivers/ with llvm-gcc and the rest with
gcc-4.2 (I have a wrapper script), I am compiling to