search for: gcc3

question about: http://llvm.org/docs/FAQ.html#translatec++ "With llvm-gcc3, this will generate program and program.bc." Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? I have 'llvm-g++ (GCC) 4.2.1 (Based on Apple Inc. build 5546) (LLVM build)' installed on Ubuntu and followed that guide and it creates indeed no .bc file. Regards, -mr

...> cadmium:/work/dl/Audio/streaming/ices-0.2.3 # /usr/local/icecast/bin/ices > > --help /usr/local/icecast/bin/ices: error while loading shared libraries: > > libgcc_s.so.1: cannot open shared object file: No such file or directory > > It looks to me like ibgcc_s.so.1 is part of gcc3. I to happen to have gcc3 > installed in /opt/experimental, but I seriously doubt that configure or > make found it by accident. Well, my guess is that I _should_ be using gcc3. I've actuall never done that before, do I manuall set CC=gcc3 in the Makefile? At any rate, I added /opt/exper...

On Wed, Sep 17, 2008 at 1:31 PM, Michael Reichenbach <michael_reichenbach at freenet.de> wrote: > question about: > http://llvm.org/docs/FAQ.html#translatec++ > "With llvm-gcc3, this will generate program and program.bc." > > Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? Those instructions are out of date; the current version of llvm-gcc doesn't generate bitcode files unless you explicitly ask it to generate them. The correct procedur...

[This is a follow up on gcc3 vs. gcc4 discussion. Background: R benchmark tests ( http://www.sciviews.org/benchmark/index.html ) show a dramatic difference in "Escoufier's method on a 37x37 matrix (mixed)" test when comparing binaries for PowerPC compiled with gcc3 vs gcc4.] On Oct 16, 2006, at 11:29 AM,...

...version. With recent changes, the current version of LLVM will no longer read old assembly or bytecode files. The upgrade path from 1.X to 2.0 is now provided by the new llvm-upgrade tool. See: http://llvm.org/docs/CommandGuide/html/llvm-upgrade.html for details on how to use this command. llvm-gcc3 generates old assembly code that will no longer assemble correctly when read by gccas. The change to llvm-gcc3 necessary to get it to emit the new instruction formats is too complicated since there is an alternative: llvm-gcc4. Consequently, we are dropping support for llvm-gcc3 as of today. How...

...the > llvm-gcc/llvm-g++ distribution). If you use "llvm-g++ -lstdc++" it > should link in whatever libstdc++ functions are needed by your program; > they will get translated to C code along with the rest of your program > when you use llc. Note that that only works with llvm-gcc3. With llvm-gcc4 you need to compile libstdc++ to bytecode explicitly. -Chris -- http://nondot.org/sabre/ http://llvm.org/

Well it was lame I was tryng to install...gives me the missing gcc3 error. So now I guess iI have to find gcc3. Maybe I should just go back to RedHat 6.2. This all worked just fine on that. # export CC=gcc3 # ./configure --with-fileio=lame --without-vorbis --disable-gtktest --enable-nasm --enable-expopt=full --prefix=/usr loading cache ./config.cache checking h...

...+ distribution). If you use "llvm-g++ -lstdc++" it > > should link in whatever libstdc++ functions are needed by your program; > > they will get translated to C code along with the rest of your program > > when you use llc. > > Note that that only works with llvm-gcc3. With llvm-gcc4 you need to > compile libstdc++ to bytecode explicitly. In llvm-gcc3 where could I find the bytecode version of libstdc++ ? Thanks. Napi

Hello, I have tried to build ices both from CVS and from the latest tarball from the web site (using a varienty of configure options, or autogen.sh in the case of cvs). Whenever I try to run it I get errors: cadmium:/work/dl/Audio/streaming/ices-0.2.3 # /usr/local/icecast/bin/ices --help /usr/local/icecast/bin/ices: error while loading shared libraries: libgcc_s.so.1: cannot open shared object

Eli Friedman schrieb: > On Wed, Sep 17, 2008 at 1:31 PM, Michael Reichenbach > <michael_reichenbach at freenet.de> wrote: >> question about: >> http://llvm.org/docs/FAQ.html#translatec++ >> "With llvm-gcc3, this will generate program and program.bc." >> >> Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? > > Those instructions are out of date; the current version of llvm-gcc > doesn't generate bitcode files unless you explicitly ask it to > generate...

...t suite? Or is it so > independent that I should put it totally elsewhere in the file > system? It's independent, put it somewhere else :) > (4) The page http://llvm.org/docs/GettingStarted.html#checkout says to get > the gcc 3.4 source code. The link above is for accessing llvm-gcc3 which was based on gcc 3.4 source code. > The instructions to compile it in http://llvm.org/docs/CFEBuildInstrs.html > seem to deal in gcc 3 and gcc 4 instead. Is this an error in the > documentation, or does it indicate that I should compile the llvm-gcc 3.4 > source code with GNU...

...o world\n"); > return 0; > } > > Next, compile the C file into a native executable: That part about "native" -- yeah, it's there. The existence predicate returns true. IT'S SOMETHING THAT IS EASILY SKIPPED OVER WHEN SKIMMING THE DOCUMENT BECAUSE, HECK, THE GCC3 DRIVER COMPILES DIRECTLY TO BYTECODE SO WHY DOESNT GCC4? It's a "least surprise" issue. If gcc3 produces bytecode directly, why did the gcc4 driver create such a large departure from original, expected functionality? It's a rhetorical question, BTW.

I just downloaded the CVS version of llvm and llvm-test. Presumably this is the one that's scheduled to become 1.8 in a few days. (1) To install llvm, do I really need the llvm version of the gcc front end? I have no special interest in yet another c/c++ conmpiler. (2) If I need llvm gcc, will the binary version suffice, or do I need to compile the CVS version? (3) If I need its source

...u 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. Ok. I'm confused. Do you want llvm-gcc3 or llvm-gcc4? The tarball above is a binary for llvm-gcc4 for Mac x86. You don't need to compile anything or fix any headers. >> Let me know if that doesn't work. > > Again: there is no fixheader-script like you describe here http:// > llvm.org/docs/GettingStarted.html#qui...

...with target all Error: Target com.apple.build returned: shell command "cd "/opt/local/var/db/dports/build/file._opt_local_var_db_dports_sources_rsync.rsync.opendarwin.org_dpupdate_dports_audio_ices2/work/ices-2.0.0" && make all" returned error 2 Command output: depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -ffast-math -fsigned-char -I/opt/local/include -I/opt/local/include/libxml2 -I/opt/local/include -g -O2 -c `test -f 'encode.c' || echo './'`encode.c source='playlist_basic.c' object='playlist_basic.o' libtool=...

...e "llvm-g++ -lstdc++" it >>> should link in whatever libstdc++ functions are needed by your program; >>> they will get translated to C code along with the rest of your program >>> when you use llc. >>> >> Note that that only works with llvm-gcc3. With llvm-gcc4 you need to >> compile libstdc++ to bytecode explicitly. >> > > In llvm-gcc3 where could I find the bytecode version of libstdc++ ? > You can download llvm-gcc3 from here (look for the LLVM-GCC 3.4 frontend for your platform): http://llvm.org/releases/...

...t; 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 describe here http:// llvm.org/docs/GettingStarted.html#quickstart. (in the gcc3 frontends there are fixheader-scripts, but there is no gcc3-frontend for darwin intel/x86) And I think it is necessary. Some gcc output: ------------------------------------------------------------------------ ------ localhost:~/llvm/test moser$ llvm-gcc -v main.c Using built-in specs. Target:...

...evel language enough to compile the abstractions of LLVM Assembly code. --Sam Crow --- On Wed, 9/17/08, Michael Reichenbach <michael_reichenbach at freenet.de> wrote: > From: Michael Reichenbach <michael_reichenbach at freenet.de> > Subject: Re: [LLVMdev] bc file only with llvm-gcc3? > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Date: Wednesday, September 17, 2008, 5:39 PM > Dale Johannesen schrieb: > > On Sep 17, 2008, at 2:36 PMPDT, Michael Reichenbach > wrote: > >> No matter if I try " > >> llvm-g++...

...t that I should put it totally elsewhere in the file >> system? > > It's independent, put it somewhere else :) > >> (4) The page http://llvm.org/docs/GettingStarted.html#checkout says to get >> the gcc 3.4 source code. > > The link above is for accessing llvm-gcc3 which was based on gcc 3.4 > source code. > >> The instructions to compile it in http://llvm.org/docs/CFEBuildInstrs.html >> seem to deal in gcc 3 and gcc 4 instead. Is this an error in the >> documentation, or does it indicate that I should compile the llvm-gcc 3.4 >&...

...If we're just installing the binary > version, does anything need to be done in order to let llvm find the > libraries, such as modifying the DLYD_LIBRARY_PATH, or are all the paths > relative? There aren't any shared libraries so the library path doesn't matter. For llvm-gcc3, the path needs to be able to find gccas and gccld from the LLVM build. For llvm-gcc4, everything is linked in statically so after llvm-gcc4 is built, it doesn't matter where LLVM lives. > What about for the stuff compiled by llvm-gcc, does that need > paths to be set as well? It shou...