[LLVMdev] Compiling glibc with LLVM

Nipun Arora nipun at cs.columbia.edu
Thu Jan 26 08:29:10 PST 2012


Hi James,

I will look into the RedHat newlib library, however, we def are looking for
a solution for GCC as well, but maybe newlib would be a good way to go to
test our complete workflow before putting an effort to  use glibc.

btw. I did have another question, hopefully you would be able to answer,
what we are looking to do is to get the control flow graph including some
sort of alias analysis for function pointers. I see that there are already
existing analysis passes in LLVM to get the control flow, however do you
know how function pointer can be handled?

Thanks
Nipun

On Thu, Jan 26, 2012 at 11:06 AM, James Molloy <james.molloy at arm.com> wrote:

>  Hi Nipun,****
>
> ** **
>
> As you say, glibc is rather GCC –oriented. I certainly haven’t tried this
> myself, but have you thought of using an alternate C library such as RedHat
> newlib? That can certainly be compiled by clang (we do it every night).***
> *
>
> ** **
>
> Cheers,****
>
>
> James****
>
> ** **
>
> *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On
> Behalf Of *Nipun Arora
> *Sent:* 26 January 2012 15:54
> *To:* LLVM Developers Mailing List
> *Subject:* [LLVMdev] Compiling glibc with LLVM****
>
> ** **
>
> Hi,****
>
> ** **
>
> I read on the gentoo website http://en.gentoo-wiki.com/wiki/Llvm that
> glibc cannot be compiled using llvm because of some GNU extensions which
> LLVM does not support.****
>
> ** **
>
> Has there been any success in compiling glibc using LLVM so as to get the
> bytecode?****
>
> We are looking to do whole program analysis to look at control flows
> including those in libc... we were hoping that we could get the control
> flows using LLVM API's for glibc.****
>
> ** **
>
> Has anyone tried this before?****
>
> ** **
>
> Thanks****
>
> Nipun****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120126/db113390/attachment.html>


More information about the llvm-dev mailing list