similar to: [LLVMdev] Embedded C Extensions

hi! i was working on an llvm-gcc4_2 version, which i used as a starting-point for a fixed-point c-datatype implementation. i read that the svn repos is up now, and so i remembered the following lines: > On Fri, 23 Mar 2007, Peter Wiedermann wrote: > > i fixed some major bugs in the llvm-gcc4_2 patch since my last post. > > this brings me to an interesting question: > >

> > i was working on an llvm-gcc4_2 version, which i used as a starting-point for > > a fixed-point c-datatype implementation. > > i read that the svn repos is up now, and so i remembered the following lines: > > > >> On Fri, 23 Mar 2007, Peter Wiedermann wrote: > >>> i fixed some major bugs in the llvm-gcc4_2 patch since my last post. >

Dear Chris, On Feb 14, 2007, at 12:33 AM, Chris Lattner wrote: >> b) introduce new types for llvm that handle types such as >> __Fract, __Accum and _Sat. >> again, comments are highly appreciated. > > My understanding of these operations is that they are basically > integer > data types whose operators have special semantics. As such, I'd > suggest

On Tue, 13 Feb 2007, Dietmar Ebner wrote: > II) Embedded C Extensions [2,3] > there's a ongoing project in gcc [4] that aims to implement > embedded c extensions > for gcc. it appears that the portions belonging to the frontend > are already pretty > stable. are there already people working on getting those bits > into llvm? Nope, I'm not aware of anyone

> It builds here (Linux x86_64), I use the following configure line: > ../llvm-gcc4.2/configure > --prefix=/home/edwin/llvm-svn/obj42/../install --program-prefix=llvm- > --enable-llvm=/home/edwin/llvm-svn/llvm/ --disable-multilib > --enable-checking=release --enable-languages=c,c++ I'm using (x86-64 linux, gcc 4.3) ../gcc-4.2.llvm/configure --prefix=/usr/local/gnat-llvm

Not sure if that's related, but we had two failures last night as well: MacOS/Universal build failed on rev 54197, when building the x86->ppc cross: cc1: warnings being treated as errors /Users/julien/buildbot/llvm/gcc-build/src/gcc/cp/pt.c:5296: warning: no previous prototype for 'outermost_tinst_level' make[2]: *** [cp/pt.o] Error 1 MingW failed on rev 54208:

Hi Bill, This is probably due to the llvm-gcc merge. Please take a look. Thanks, Evan On Jul 30, 2008, at 10:04 AM, Duncan Sands wrote: > x86-64 linux, during stage3: > > xgcc -B/home/duncan/LLVM/gcc-4.2.llvm-objects/./gcc/ -B/usr/local/ > gnat-llvm/x86_64-unknown-linux-gnu/bin/ -B/usr/local/gnat-llvm/ > x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/gnat-llvm/x86_64-

Anyone else seeing this? LLVM/gcc-4.2.llvm-objects/./gcc/xgcc -BLLVM/gcc-4.2.llvm-objects/./gcc/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/bin/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/include -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/sys-include -c -DHAVE_CONFIG_H -O2 -g -O2 -I.

x86-64 linux, during stage3: xgcc -B/home/duncan/LLVM/gcc-4.2.llvm-objects/./gcc/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/bin/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/include -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I../../../gcc-4.2.llvm/libgomp -I.

I am new to LLVM, and I'm trying to compile llvm and llvm-gcc from subversion on a Solaris10/SPARC machine. I have already tried building llvm-2.4 on this machine, but it failed. I then tried the subversion sources (rev. # 65253 fro llvm and rev#65263 for llvm-gcc) and llvm at least builds correctly ( I however have not tried testing it!). I can execute binaries located in

On 2008-10-01 17:36, Duncan Sands wrote: >> It builds here (Linux x86_64), I use the following configure line: >> ../llvm-gcc4.2/configure >> --prefix=/home/edwin/llvm-svn/obj42/../install --program-prefix=llvm- >> --enable-llvm=/home/edwin/llvm-svn/llvm/ --disable-multilib >> --enable-checking=release --enable-languages=c,c++ >> > > I'm using

>> Dear All, I have been trying for days but still cannot break this barrier. May I get your help? I have compiled llvm-2.1 successfully and make install. When I proceed with llvm-gcc-4.2-2.1, however, I keep getting linking error as attached. Some functions with totally different content conflict with each other in linking process. That is a Linux box (Debian, with 2.6.23-1

On 2008-10-01 15:04, Duncan Sands wrote: > Anyone else seeing this? > > LLVM/gcc-4.2.llvm-objects/./gcc/xgcc -BLLVM/gcc-4.2.llvm-objects/./gcc/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/bin/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/include -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/sys-include -c

>> In addition to this, I've checked in the first draft of the release >> notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/ >> ReleaseNotes.html). > > The release notes mention llvm-gcc 4.2, but the prerelease only included > llvm-gcc 4.0. Is the final release going to include 4.0 or 4.2 or both? I will be releasing a source tar ball of llvm-gcc4.2, but

Hi John, > I am trying to build llvm-gcc4.2-2.6. > > My configure options are > > $ /local/tools/lin32/llvm-gcc4.2-2.6/bin/llvm-gcc -v > Using built-in specs. > Target: i686-linux > Configured with: ../llvm-gcc4.2-2.6.source/configure --prefix=/local/tools/lin32/llvm-gcc4.2-2.6 --disable-nls --enable-shared --enable-threads=posix --enable-languages=c,c++ --with-gnu-as

Hello. My goal is to use LLVM with JIT compiler for ARM on Android device. Currently I have successfully built and executed LLVM bitcode with interpreter on Android. Speed is not so great, that is why I want to use JIT. I tried building bitcode on windows with llvm-gcc that is provided on llvm home page. Resulting bitcode runs great in interpreter, but it doesn't use JIT. From what I

hi all, I was trying to build the latest LLVM gcc front end and it failed. rajika@:~/project/llvm/dst-directory$ svn info | grep URL URL: http://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk configure option: ../dst-directory/configure --prefix=/usr/local/ --enable-llvm=/home/rajika/project/llvm/llvm-objects it gave me the following errors ../../dst-directory/gcc/llvm-convert.cpp:1163: error:

On Wed, Mar 19, 2008 at 12:11 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Bill, thanks for fixing it. > No prob! :-) > > > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c: In function 'ix86_expand_convert_uns_DI2DF_sse': > > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c:10270: warning: large integer implicitly truncated to unsigned type

Forgot to mention. I don't know how well the canadian cross compile stuff works in 2.5. We made some improvements in that area for 2.6. If you have trouble with it, I'd suggest trying 2.6 (or even better, ToT svn) and seeing if things are improved there. -Jim On Sep 25, 2009, at 2:04 AM, Martins Mozeiko wrote: > Hello. > > My goal is to use LLVM with JIT compiler for ARM

Hello, Pazzo > I had a look to llvm (2.6) configure options but I couldn't find any > way to specify cpu type, fpu ecc.. These are not llvm configure options, but gcc's one. Basically, you should configure llvm-gcc in the same way you do for gcc for your platform. > Could you please give me any > indication and/or example? I want to try llvm with Atmel's > AT91SAM7X256