similar to: [LLVMdev] About llvm's capability

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] About llvm's capability"

2009 Sep 08
0
[LLVMdev] About llvm's capability
On Sep 7, 2009, at 6:43 PM, kito wrote: > Hello everybody > > I am newbie in llvm and compiler, I have some questions about llvm's > capability - How large project llvm can compile now? > I mean, such as linux kernel or ggc...llvm can build it? > especially on the other architecture, ARM or alpha > because I must choice one between gcc and llvm to study. > In my long
2008 Feb 16
0
[LLVMdev] linux/x86-64 codegen support
Andrew Lenharth wrote: > Interestingly, in the .i file there are 2 __builtin_alloca, and > EmitBuiltinAlloca is only being called once. > > Hmm, here EmitBuiltinAlloca gets called twice, but it looks like validate_arglist is rejecting the args both times. I have 2 calls to alloca generated: $ grep alloca x.bc|grep call %tmp21 = call i8* @alloca( i64 %tmp20 ) nounwind
2011 Mar 22
0
[LLVMdev] -emit-llvm on ubuntu is broken
Looks like something wonky with DragonEgg. Duncan? -eric On Mar 21, 2011, at 7:05 PM, stackunderflow wrote: > > Hi Eric, > > here is my -emit-llvm -S -v output: > > Using built-in specs. > COLLECT_GCC=gcc-4.5 > COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper > Target: i686-linux-gnu > Configured with: ../src/configure -v
2011 Mar 22
4
[LLVMdev] -emit-llvm on ubuntu is broken
Hi Eric, here is my -emit-llvm -S -v output: Using built-in specs. COLLECT_GCC=gcc-4.5 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.1-7ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
2011 Mar 22
2
[LLVMdev] -emit-llvm on ubuntu is broken
Hi Eric, > Looks like something wonky with DragonEgg. you need to use -fplugin-arg-dragonegg-emit-ir or -flto with dragonegg, not -emit-llvm. Also, you currently have to use -S (getting human readable IR) rather than -c because with -c gcc will run cc1 with -S (getting human readable IR) then pass the result to the system assembler which of course barfs. This is documented on the web-page
2007 May 26
1
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi Warren, you can try to configure with the following export CFLAGS="-m64" export LDFLAGS="-L/usr/lib64" LLVM: ../src/configure --prefix=`pwd`../install --enable-optimized --enable-jit --enable-targets=host-only make LLVM-GCC: ../llvm-gcc4-2.0.source/configure --prefix=`pwd`../install --program-prefix=llvm- --enable-llvm=/home/warren/llvm/obj/ --enable-languages=c,c++
2011 Jun 08
5
[PATCH] ioemu: IGFX passthrough fix SNB GGC
The GGC field have moved from 0x52 to 0x50 on Sandy Bridge. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2004 Jan 09
1
Problem with DNS (UDP) queries
Hi all I am trying to get rid of strings: kernel: Connection attempt to UDP FREEBSD_IP:port from DNSSERVER_IP:53 on my console and in log file I understand that those are replies on DNS queries that for some reason took too long time to be answered. I do not want to turn off the "log in vain" feature. As these strings fill up my log I am afraid to miss some sensitive messages (e.g.
2005 Nov 28
2
[LLVMdev] Help setting up a llvm project
First I'd like to let you know I've started working on porting gcjx to llvm. Some other intrested people may help but I've just started the project. My first question is I'm porting gcjx over to use the llvm build system I've successfully created a number of libraries but gcjx uses a number of sub directories for its source and I'd like the .o files for all of them to
2013 Feb 26
2
[LLVMdev] make error building llvm/clang 3.2 on Linux
Just in case someone is having similar problems and/or following this thread, here's my final "solution" (at least, for now). In my bash build script, prior to configure, I set the C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to empty strings, and then set some other environment variables instead: export C_INCLUDE_PATH= export CPLUS_INCLUDE_PATH=
2007 May 26
0
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi Warren, You have the -m32 flag set, but it's still giving you this: > Warning: Generation of 64-bit code for a 32-bit processor requested. > Warning: 64-bit processors all have at least SSE2. But are you sure you want to compile the LLVM-GCC source? You should use the binaries unless absolutely necessary. -bw On May 24, 2007, at 10:34 PM, Warren Armstrong wrote: > Hi all,
2007 May 25
3
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi all, I've run into problems compiling the llvm-gcc frontend on x86_64. Is this not supported, or am I making an error somewhere? The procedure I followed was: 1. Download LLVM 2.0 source as a tarball (from a few days ago, during the testing phase). 2. Download the llvm-gcc4 source today, as a tarball. 3. Extract both. 4. Configure LLVM as: ../src/configure --prefix=`pwd`../install
2005 Nov 28
0
[LLVMdev] Help setting up a llvm project
Hi Mike, Sounds like an interesting project. Here's some ideas for you on the LLVM Makefile System. If you haven't, I *strongly* suggest you read the makefile and project documentation (docs/MakefileGuide.html and docs/Projects.html). There is much information there that you need to understand. LLVM is set up so that a single directory builds a single result. Since your source code
2005 May 14
2
[LLVMdev] Building Cygwin binaries
Hi, I have got GCC 3.4.3 and binutils 2.15 installed on Cygwin. Had to copy as.exe to gccas.exe to get llvm-gcc to get this far. I am getting the following error message(s) :- /usr/build/llvm-gcc/gcc/xgcc -B/usr/build/llvm-gcc/gcc/ -B/usr/llvm-gcc/i686-pc- cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem /usr/llvm-gcc/i686-pc-c ygwin/include -isystem
2006 Nov 14
2
[LLVMdev] gcc 4 frontend binary for mac os x x86
Hi, On Nov 13, 2006, at 9:17 PM, Tanya M. Lattner wrote: > I assume you have an Mac with an Intel processor. Yes. Sorry, I forgot to mentioned it in the mailbody. > Download this: > http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz I think that is the same tarball I used before. > Let me know if that doesn't work. Again: there is no fixheader-script like you
2009 Aug 06
2
xyplot and subscripts
Hi all, I have a data frame like this: DF <- data.frame(x = rnorm(10), y = rnorm(10), gr = rep(1:5, 2)) and I make the following xy-plot: library(lattice) xyplot(y ~ x, data = DF, groups = gr, type = "b", col = 1) Is it possible that the two points that belong to the same group specified by DF$gr to have a different color -- that is for each pair of points connected by the line,
2012 Dec 07
0
[LLVMdev] Increase the number of registers in ARM
> I almost change all the instruction formats. It was a huge work. I am going > to compile and run it now. We have done the similar work[1] on this topic by gcc and we have start migrate our platform to LLVM. In my experience, you need to take care the follow part: * ARMBaseRegisterInfo::getRegPressureLimit * ARMBaseRegisterInfo::getRawAllocationOrder * CalleeSavedRegs *
2013 Aug 02
1
segfault and RunSnowWorker: not found
Hi, While I suspect that this is an issue peculiar to my machine (Debian squeeze amd64, R version 3.0.1, up-to-date packages), I'm hoping that somebody on this list may be able to give me suggestions on how to troubleshoot and fix the following: > library (snow) > cl <- makeSOCKcluster(c("localhost","localhost")) sh: 1: RunSnowWorker: not found I presume/hope
2012 Dec 07
2
[LLVMdev] Increase the number of registers in ARM
I almost change all the instruction formats. It was a huge work. I am going to compile and run it now. Best Regards, A. Yazdanbakhsh >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> PhD. Student School of Electrical and Computer Engineering University of Wisconsin-Madison E-mail: yazdanbakhsh
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=utf-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Reid,<br> <br> Here's the backtrace you asked for:<br> <br>