search for: llvmlinux

I'd like to announce the LLVMLinux project. This project aims to fully build the Linux kernel using Clang/LLVM on the various architectures supported by the Linux kernel. The project consolidates the work of the lll-project, the PAX team, and Mark Charlebois' work on the ARM kernel. http://llvm.linuxfoundation.org <http:/...

...ep 7, 2012 at 10:03 AM, <llvmdev-request at cs.uiuc.edu> wrote: > > Message: 1 > Date: Thu, 06 Sep 2012 21:58:52 -0400 > From: Behan Webster <behanw at converseincode.com> > To: "llvmdev at cs.uiuc.edu" <llvmdev at cs.uiuc.edu> > Subject: [LLVMdev] The LLVMLinux Project > Message-ID: <504954DC.3010708 at converseincode.com> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > I'd like to announce the LLVMLinux project. This project aims to fully > build the Linux kernel using Clang/LLVM on the v...

On 10/10/13 22:01, Jakob Stoklund Olesen wrote: > On Oct 10, 2013, at 12:32 PM, Behan Webster <behanw at converseincode.com> wrote: > >> One of the issues the LLVMLinux project is having is with the use of >> named registers in the Linux kernel code. The kernel uses something like >> this in order to assign a C variable name to a register (one for each >> kernel arch). >> >> register unsigned long current_stack_pointer asm("es...

On 20/10/2013 16:22, Behan Webster wrote: > On 10/10/13 22:01, Jakob Stoklund Olesen wrote: >> On Oct 10, 2013, at 12:32 PM, Behan Webster <behanw at converseincode.com> wrote: >> >>> One of the issues the LLVMLinux project is having is with the use of >>> named registers in the Linux kernel code. The kernel uses something like >>> this in order to assign a C variable name to a register (one for each >>> kernel arch). >>> >>> register unsigned long current_stack_...

On Oct 10, 2013, at 12:32 PM, Behan Webster <behanw at converseincode.com> wrote: > One of the issues the LLVMLinux project is having is with the use of > named registers in the Linux kernel code. The kernel uses something like > this in order to assign a C variable name to a register (one for each > kernel arch). > > register unsigned long current_stack_pointer asm("esp"); > &gt...

One of the issues the LLVMLinux project is having is with the use of named registers in the Linux kernel code. The kernel uses something like this in order to assign a C variable name to a register (one for each kernel arch). register unsigned long current_stack_pointer asm("esp"); clang doesn't allow this kin...

On 11/05/13 00:20, Alp Toker wrote: > On 20/10/2013 16:22, Behan Webster wrote: >> On 10/10/13 22:01, Jakob Stoklund Olesen wrote: >>> On Oct 10, 2013, at 12:32 PM, Behan Webster <behanw at converseincode.com> wrote: >>> >>>> One of the issues the LLVMLinux project is having is with the use of >>>> named registers in the Linux kernel code. The kernel uses something like >>>> this in order to assign a C variable name to a register (one for each >>>> kernel arch). >>>> >>>> register unsigned...

...089 apply cleanly. * r226171 - [mips] Fix a typo in the compare patterns for MIPS32r6/MIPS64r6. o Fixes bad code generation in the test-suite for certain option combinations. * r225529 - [mips] Add support for accessing $gp as a named register. o Fixes bad code generation in LLVMLinux * r224425 and r225521 - [mips] Set GCC-compatible MIPS asssembler options before inline asm blocks. o Fixes bad code generation in LLVMLinux o Makes our inline assembly compatible with GCC's. If you're ok with these then I'll start merging them in advance of 3.5.2-rc1....

I'll look. On May 16, 2014 8:01 AM, "Jan-Simon Möller" <dl9pf at gmx.de> wrote: > The unrecognized junk is (path shortened, so don't worry): > > .Ldebug_range: > .file 1 "/src/linux/include/linux" "export.h" > .file 2 "/src/linux/init" "main.c" > .file 3

Hi all, I'm trying to generate whole program bitcode files for linux kernel and do interprocedural analysis on kernel. I use llvmlinux to compile kernel with clang and generate a bunch of bitcode files successfully. I need to link all these bitcode files together into a single bitcode file, so that I can run whole program analysis. Can I use llvm-link to achieve this? Or should I use libLTO to link all these bitcode files togeth...

Hi ! Our buildbot found this regression while compiling the kernel with clang: A bisection points to 475ac5d302ba84ac13d34a9215c29c1a38ca5690 is the first bad commit commit 475ac5d302ba84ac13d34a9215c29c1a38ca5690 Author: Eric Christopher <echristo at gmail.com> Date: Thu May 15 01:10:50 2014 +0000 Unify command line handling of MCTargetOptions and remove extra options and

...need to use the SVN > tags, $ clang --version currently gives me "clang version 3.8.0 > (tags/RELEASE_380/final)") > In the meantime I created source-tarballs out of my local Git repos and built a llvm-toolchain v3.8.1 successfully. I will test it with my local version of "llvmlinux-amd64" Linux-kernel. - Sedat - > Jonas > >> -----Original Message----- >> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Sedat >> Dilek via llvm-dev >> Sent: Monday, June 27, 2016 9:16 AM >> To: Anton Korobeynikov >> Cc: llvm...

11.10.2013, 01:39, "Jakob Stoklund Olesen" <stoklund at 2pi.dk>: > On Oct 10, 2013, at 12:32 PM, Behan Webster <behanw at converseincode.com> wrote: > >>  One of the issues the LLVMLinux project is having is with the use of >>  named registers in the Linux kernel code. The kernel uses something like >>  this in order to assign a C variable name to a register (one for each >>  kernel arch). >> >>     register unsigned long current_stack_pointer asm(&quo...

Hi Dmitry, thanls for sharing. Few comments/questions below: >Here is the list of modifications I had to do in order to link the kernel (I have used llvmlinux with clang and mainline with gcc, the >results are similar): > >1. LLD patches: > - D28094 (Implemented support for R_386_PC8/R_386_8 relocations) Do you remember where it was used ? >5. In arch/x86/kernel/vmlinux.lds.S commented out the "CONSTRUCTORS", because LLD doesn...

Hi, I am new to LLVM I want to use llvm and clang on Android, I have downloaded android toolchain and did the configure for llvm using the following commad ./configure --build=arm-linux-androideabi --host=arm-linux-androideabi --target=arm-linux-androideabi --with-float=hard --with-fpu=neon --enable-targets=arm --enable-optimized --enable-assertions and was getting the error "checking

...On 11/05/13 09:26, Konstantin Tokarev wrote: >> >> 11.10.2013, 01:39, "Jakob Stoklund Olesen" <stoklund at 2pi.dk>: >>> On Oct 10, 2013, at 12:32 PM, Behan Webster <behanw at converseincode.com> wrote: >>> >>>> One of the issues the LLVMLinux project is having is with the use of >>>> named registers in the Linux kernel code. The kernel uses something like >>>> this in order to assign a C variable name to a register (one for each >>>> kernel arch). >>>> >>>> register unsigne...

...NU (such as glibc) rely on their own > non-standard extensions. Simply put: If you want to use one, you must use > all. The case extends to binutils, gcc, etc. > Mainline Linux and glibc are likely to depend on GCC for the foreseeable future, but you may be interested in investigating the LLVMLinux project, which has a fork of the kernel that compiles with clang: http://llvm.linuxfoundation.org/index.php/Main_Page -Joe -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130330/70afd1c4/attachment.html>

Hi Venkata, > ./configure --build=arm-linux-androideabi --host=arm-linux-androideabi > --target=arm-linux-androideabi --with-float=hard --with-fpu=neon > --enable-targets=arm --enable-optimized --enable-assertions Renato's suggestion is a good one, but I suspect the immediate problem here is that this configure line is for building *on* an ARM board. You're probably executing

Hi all, I'm trying to generate whole program bitcode files for linux kernel and do interprocedural analysis on kernel. I use llvmlinux to compile kernel with clang and generate a bunch of bitcode files successfully. I need to link all these bitcode files together into a single bitcode file, so that I can run whole program analysis. Should I use libLTO to link all these bitcode files together? I guess I have to modify the linux k...

On 11/05/13 09:26, Konstantin Tokarev wrote: > > 11.10.2013, 01:39, "Jakob Stoklund Olesen" <stoklund at 2pi.dk>: >> On Oct 10, 2013, at 12:32 PM, Behan Webster <behanw at converseincode.com> wrote: >> >>> One of the issues the LLVMLinux project is having is with the use of >>> named registers in the Linux kernel code. The kernel uses something like >>> this in order to assign a C variable name to a register (one for each >>> kernel arch). >>> >>> register unsigned long current_st...