[llvmlinux] Linux Kernel LLVM IR

Mark Charlebois charlebm at gmail.com
Mon Mar 4 17:06:20 UTC 2013


Yes, there are variables to set the commit to use for both the kernel and
for Clang and LLVM.

I would also recommend using the vexpress target at least for now as it
requires the fewest patches and works with the upstream kernel.

If you look in toolchain/clang/clang.mk you will see the following:

LLVM_COMMIT    = "baabdecbb9bf5b32fa81b1e2830ab13076d549f1"
CLANG_COMMIT   = "953a61f26bf79932b9699b09add4c388764de170"

These set the version of clang and LLVM to use to currently work around an
issue with the latest version of clang that segfaults when building the
kernel.

-Mark

On Mon, Mar 4, 2013 at 8:11 AM, Marcelo Sousa <marceloabsousa at gmail.com>wrote:

> Can I specify somewhere my version of the linux kernel and my version
> of LLVM? I just want to produce the bytecode files.
>
> On Mon, Mar 4, 2013 at 4:07 PM, Behan Webster <behanw at converseincode.com>
> wrote:
> > On 03/04/13 10:57, Marcelo Sousa wrote:
> >>
> >> Hello,
> >>
> >> I'm getting the following error when trying to build x86:
> >>
> >> ---------------------------------------------------------------------
> >> Patching LLVM...
> >> ---------------------------------------------------------------------
> >> (cd /home/scratch/llvm-setup/toolchain/clang/src/llvm && quilt push -a)
> >> Applying patch
> patches/0002-pax-linux-llvm-x86_handle-empty-archive.patch
> >> can't find file to patch at input line 15
> >> Perhaps you used the wrong -p or --strip option?
> >> The text leading up to this was:
> >> --------------------------
> >> |From 7cb2d39b461c58df2583a6881f42b18c30f1eafb Mon Sep 17 00:00:00 2001
> >> |From: =?UTF-8?q?Jan-Simon=20M=C3=B6ller?= <dl9pf at gmx.de>
> >> |Date: Tue, 10 Jul 2012 12:37:24 +0200
> >> |Subject: [PATCH 2/6] pax-linux-llvm x86_handle-empty-archive.patch
> >> |
> >> |Patch from series at
> >>
> >>
> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120507/142707.html
> >> by PaX Team.
> >> |---
> >> | lib/Linker/LinkItems.cpp |    5 ++++-
> >> | 1 files changed, 4 insertions(+), 1 deletions(-)
> >> |
> >> |diff --git a/lib/Linker/LinkItems.cpp b/lib/Linker/LinkItems.cpp
> >> |index 52a0d17..2782196 100644
> >> |--- a/lib/Linker/LinkItems.cpp
> >> |+++ b/lib/Linker/LinkItems.cpp
> >> --------------------------
> >> No file to patch.  Skipping patch.
> >> 1 out of 1 hunk ignored
> >> Patch patches/0002-pax-linux-llvm-x86_handle-empty-archive.patch does
> >> not apply (enforce with -f)
> >> make: *** [/home/scratch/llvm-setup/toolchain/clang/state/llvm-patch]
> >> Error 1
> >>
> >>
> >> Any ideas of what's going wrong?
> >>
> > The x86_64 build is broken (known issue). The maintainer of that target
> is
> > working on it. However he's away on business right now, so he has less
> time
> > to spend on it than normal.
> >
> > Due to the nature of our project, we need to work from the HEAD of the
> Linux
> > Kernel and LLVM project, which means things can break easily.
> >
> > We should probably provide a config file which allows you to compile an
> > eariler version of our project which does work.
> >
> > Behan
> >
> > --
> > Behan Webster
> > behanw at converseincode.com
> >
> >
> > _______________________________________________
> > LLVMLinux mailing list
> > LLVMLinux at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux
> _______________________________________________
> LLVMLinux mailing list
> LLVMLinux at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/llvmlinux/attachments/20130304/9c0a1c29/attachment-0001.html>


More information about the LLVMLinux mailing list