search for: cfrontend

Hi, When compiling the cfrontend for Linux/PPC architecture on a powermac G5, i got the following error : -------------------------------Compilation error listing if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi make GCC_FOR_TARGET="/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/xgcc -B/usr/local/home/cyri...

...gwin and building the C front-end there, please reply and CC Alex. --- Post by Alex Vinokur below --- =============== Windows 2000 GNU gcc 3.3.3 (cygwin special) =============== ./configure ./make I have got compilation error ------------------------------- make[1]: Entering directory `/dir1/cfrontend/src/libiberty' make[2]: Entering directory `/dir1/cfrontend/src/libiberty/testsuite' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/dir1/cfrontend/src/libiberty/testsuite' make[1]: Leaving directory `/dir1/cfrontend/src/libiberty' make[1]: Entering directory...

...e. qmtest.target: local And finally: Feature.cc.weirdnames /usr/home/llvm/obj/../test/Regression/C++Frontend/2003-08-28-ForwardType.cpp:3: warning: inline function `void* operator new(unsigned int, void*)' used but n ever defined /usr/home/llvm/obj/../test/Regression/CFrontend/2002-02-18-64bitConstant.c: In function `main': /usr/home/llvm/obj/../test/Regression/CFrontend/2002-02-18-64bitConstant.c:3: warning: return type of 'main' is not `int' /usr/home/llvm/obj/../test/Regression/CFrontend/2002-04-08-LocalArray.c: In function `test': /usr/home/llvm...

Cyrille Mescam wrote: > Hi, > > > When compiling the cfrontend for Linux/PPC architecture on a powermac > G5, i got > the following error : I hate to ask a silly question, but are you using "make bootstrap" to build the cfrontend? Your output looks like gccas is being given a native code assembly language file to parse, and I seem to recal...

...might shed more light on this problem? Patrick We will use: 176.gcc Compiling Binaries Building 176.gcc ref base ppc32_llvm default specmake clean 2> make.err | tee make.out rm -rf cc1 cc1.exe *.o core *.err *.out specmake build 2> make.err | tee make.out /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o c-parse.o -DHOST_WORDS_BIG_ENDIAN -O3 c-parse.c /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o c-lang.o -DHOST_WORDS_BIG_ENDIAN -O3 c-lang.c /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o c-lex.o -DHOST_WORDS...

On Tue, 4 May 2004, Chris Lattner wrote: > I suspect that a large reason that LLVM does worst than a native C > compiler with the CBE+GCC is that LLVM generates very low-level C code, > and I'm not convinced that GCC is doing a very good job (ie, without > syntactic loops). Yup, this is EXACTLY what is going on. I took this very simple C function: int Array[1000]; void test(int

Hi Guys I'm trying to port and build the GCC Front End to the Interix environment. I've succeded until the xgcc program executes: /usr/local/src/cfrontend/build/gcc/xgcc -B/usr/local/src/cfrontend/build/gcc/ -B/usr/local/src/cfrontend/install//i586-pc-interix3/bin/ -B/usr/local/src/cfrontend/install//i586-pc-interix3/lib/ -isystem /usr/local/src/cfrontend/install//i586-pc-interix3/include -isystem /usr/local/src/cfrontend/install//i586-pc-interi...

...uild on LLVM 1.4 source (the released tarball), using Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 box, dual CPU). Before I get _too_ deep into it, I thought I would ask if the following compilation failure on the CFE looks the least bit familiar to anyone: /home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/xgcc -B/home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/ -B/usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/bin/ -B/usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/lib/ -isystem /usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/include -isystem /usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/...

...t; Patrick > > We will use: 176.gcc > Compiling Binaries > Building 176.gcc ref base ppc32_llvm default > specmake clean 2> make.err | tee make.out > rm -rf cc1 cc1.exe *.o core *.err *.out > specmake build 2> make.err | tee make.out > /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o > c-parse.o -DHOST_WORDS_BIG_ENDIAN -O3 c-parse.c > /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o > c-lang.o -DHOST_WORDS_BIG_ENDIAN -O3 c-lang.c > /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o >...

Jeff, Actually, that was my fault. I forgot to remove the non-existent directories from the configure.ac file. That's done and committed now, so the advice is still the same: update configure script :) Reid. On Sun, 2004-09-05 at 09:53, Jeff Cohen wrote: > Configure gives me these errors on FreeBSD. I'm proceding with the build anyway to see what happens. Don't worry :)

...nted yet. > And finally: > > Feature.cc.weirdnames /usr/home/llvm/obj/../test/Regression/C++Frontend/2003-08-28-ForwardType.cpp:3: warning: inline function `void* operator new(unsigned int, void*)' used but n > ever defined > /usr/home/llvm/obj/../test/Regression/CFrontend/2002-02-18-64bitConstant.c: In function `main': > > /usr/home/llvm/obj/../test/Regression/CFrontend/2002-02-18-64bitConstant.c:3: warning: return type of 'main' is not `int' > /usr/home/llvm/obj/../test/Regression/CFrontend/2002-04-08-LocalArray.c: In function `test':...

...----------------------------- EXTRA_MULTILIB_PARTS = crtbegin$(objext) crtend$(objext) \ crtbeginS$(objext) crtendS$(objext) crtbeginT$(objext) ------------------------------------------------------------- Now, it stoppes there: gmake[1]: Entering directory `/usr/local/home/cyrille/project/llvm/cfrontend/build/powerpc-unknown-linux-gnu/libiberty' if [ x"" != x ] && [ ! -d pic ]; then \ mkdir pic; \ else true; fi touch stamp-picdir CONFIG_FILES= CONFIG_HEADERS=config.h:config.in /bin/sh ./config.status config.status: creating config.h config.status: config.h is un...

...) > > Reid. > Hallo, do you know if bootstrap is the default target? This is what I'm doing: <code> inherit eutils DESCRIPTION="C, C++ Frontend for Low Level Virtual _Machine" HOMEPAGE="http://llvm.org/" SRC_URI="http://llvm.cs.uiuc.edu/releases/${PV}/cfrontend-${PV}.source.tar.gz" LICENSE="llvm" SLOT="0" KEYWORDS="~ppc ~sparc ~x86" IUSE="" DEPEND= S=${WORKDIR}/cfrontend src_unpack() { unpack ${A} cd cfrontend mkdir build } src_compile() { cd ${S}/build ../src/configure --prefix=/usr --disabl...

...ed tarball), using > Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 > box, dual CPU). Before I get _too_ deep into it, I thought I > would ask if the following compilation failure on the CFE > looks the least bit familiar to anyone: > > > /home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/xgcc > -B/home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/ > -B/usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/bin/ > -B/usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/lib/ > -isystem /usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/include > -isystem /usr/lib/llvm/cfrontend/...

...? No, "all" is the default. > > This is what I'm doing: > <code> > inherit eutils > > DESCRIPTION="C, C++ Frontend for Low Level Virtual _Machine" > HOMEPAGE="http://llvm.org/" > SRC_URI="http://llvm.cs.uiuc.edu/releases/${PV}/cfrontend-${PV}.source.tar.gz" > > LICENSE="llvm" > SLOT="0" > KEYWORDS="~ppc ~sparc ~x86" > IUSE="" > > DEPEND= > > S=${WORKDIR}/cfrontend > > src_unpack() { > unpack ${A} > cd cfrontend > mkdir build I w...

On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote: > Cyrille Mescam wrote: > >Hi, > > > > > >When compiling the cfrontend for Linux/PPC architecture on a powermac > >G5, i got > >the following error : > > I hate to ask a silly question, but are you using "make bootstrap" to > build the cfrontend? Your output looks like gccas is being given a > native code assembly language file t...

...uild of one of the tests to make sure I've got the flags right: Compiling Binaries Building 164.gzip ref base ppc32_llvm default specmake clean 2> make.err | tee make.out rm -rf gzip gzip.exe *.o core *.err *.out specmake build 2> make.err | tee make.out /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o bits.o -g -O3 bits.c /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o deflate.o -g -O3 deflate.c /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o gzip.o -g -O3 gzip.c /Users/patrick/Desktop/LLVM/cfro...

Is it safe to use the LLVM cfrontend 1.6 with LLVM 1.7 or the latest LLVM from CVS? I am running OS X 10.3.9, which I believe corresponds to Darwin kernel version 7.9.0. When I tried to use the 1.7 cfrontend, I could not get LLVM 1.7 or the LLVM from CVS to compile. However, when I used the 1.6 cfrontend (which is additionally...

...quot;strip") has been moved into the SymbolTable. This means that the SymbolStripping pass is now a single call to the SymbolTable::strip() method. These changes pass all feature tests. Some of the regression tests fail and I'm not sure if its due to (a) my changes, (b) my old cfrontend, or (c) someone else's changes. I suspect its more of (b) and (c) but I will look into this in more detail later this week. Next steps on bug 122 (each a separate commit): * Completely rid ourselves of Type::TypeTy. This involves a rewrite of the SlotCalculator which will be divided up betwe...

On Fri, 30 Apr 2004, Patrick Flanagan wrote: > Thanks! Grabbed the latest from CVS and added that linker option to the > config file. It looks like it compiles and runs the SPEC tests ok now. Great! > Just to make sure I understand how LLVM works, got a few clarifications: > > 1. The ppc code I'm generating with the -native-cbe is static, correct? Yes, it's purely static