similar to: [LLVMdev] static compilation with the LLVM C frontend

Hello, I'm trying to compile to SPEC CPU2000 suite to LLVM bytecode, using the llvm-test harness. I have tried this using: - both the 1.7 and 1.8 releases, without succes (and running into the same problems in both releases) - both the gcc3 and gcc4 frontends I'm working on Linux/x86. LLVM is configured using: ./configure --prefix=/path/to/bin/dir and compiled using gmake; gmake

On 31 Aug 2006, at 19:13, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: > >> When I adjust the settings in Makefile.nagfortran as follows, I'm >> able to get bytecode file for lucas, galgel and facerec, but make >> still quits with an error (after generating >> bytecode files for 7 (out of 26) benchmarks. >> >> Also, the file

Hi Reid, On 06 Apr 2007, at 04:51, Reid Spencer wrote: > All, > > Just in case you missed the construction of these pages, I thought > you'd > like to know about these new ones: > > http://llvm.org/DevMtgMay2007.html > All the latest details on the 25th May Developer's meeting. Page > modified daily! Do you know if there are plans for any form of live

Hi Scott, On 18 Mar 2007, at 04:22, Scott Fortmann-Roe wrote: > Hi, > > I noticed that LLVM had signed up as a mentoring organization for > Google's summer of code. LLVM looks like an exciting project that > overlaps some of my interests. > > I would be interested in developing an additional front end for a > language it does not currently support (I'm open to

Chris Lattner wrote: > Hacking on the interpreter is easy, but has several drawbacks. In > particular, the interpreter is very slow (even compared to other > interpreters) and it is missing functionality: you cannot call arbitrary > external functions, which causes many programs to fail in it. What do you mean by external functions? I only need to print stuff to file, the

Chris Lattner wrote: > On Thu, 13 Jul 2006, Kenneth Hoste wrote: >> Chris Lattner wrote: >>> Hacking on the interpreter is easy, but has several drawbacks. In >>> particular, the interpreter is very slow (even compared to other >>> interpreters) and it is missing functionality: you cannot call >>> arbitrary external functions, which causes many

John Criswell wrote: > You can compile library code into LLVM bytecode libraries and link them > with gccld. In general, LLVM provides tools equivalent to most of your > compiler tool chain (gccas, gccld, llvm-ar, llvm-nm, etc). You can, for > example, make an archive of LLVM bytecode files. > > The problem, in your case, is that no one has successfully compiled all >

On 31 Aug 2006, at 23:46, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> Bummer. I think I'll contact the NAG support for more info on >> this. Can you >> show me the content of your Makefile.nagfortran? > > It is identical to yours. > >> Also, it is possible to tell make only to compile benchmark X? How >> can I >>

Dear all, Just today, I heard of the existence of the LLVM project. Because of its high activity and projects, I'm quite interested in it for using it in my research. Currently, we are comparing applications/programs/benchmarks by collecting characteristics of their dynamic behavior. This is done by instrumenting the program (using ATOM on Alpha), and subsequently running the program.

On 19 Mar 2007, at 13:33, Kenneth Hoste wrote: > I think getting a Fortran frontend working will highly benefit the > relevance of LLVM for researchers. Quite a few of the SPEC CPU2000 > and CPU2006 benchmarks are fully or partially written in Fortran, and > the SPEC benchmarks remain by far the most important benchmarks used > in computer architecture and compiler-related

On 31 Aug 2006, at 07:58, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: >>> $ grep F95 .../projects/llvm-test/Makefile.config >> >> -bash-3.00$ grep F95 projects/llvm-test/Makefile.config >> # F95: Enable LLVM to run Fortran benchmarks without a Fortran >> front-end >> USE_F95=1 >> F95_DIR := >> F95 :=

On 30 Aug 2006, at 23:04, Chris Lattner wrote: > On Wed, 30 Aug 2006, Kenneth Hoste wrote: >>> I use NAG with llvm-gcc4. What sort of errors do you get? Did >>> you configure llvm-test with the appropriate flags to find it? >> Yes, I did. llvm-test is configured as follows: (in /work/LLVM/ >> 1.8/ llvm/project/llvm-test): >> ./configure

> I managed to solve this problem myself.... The problem was not correctly specifiying the SPEC CPU2000 source directory. configure says the dir was found, but that doesn't mean the sources will be found. For future reference: When you get the error: make[2]: *** No rule to make target `Output/accum.rbc', needed by `Output/177.mesa.linked.rbc'. Stop. You've probably

On 25 Nov 2006, at 09:02, Reid Spencer wrote: > Anyone know what to do about this: > > make[4]: Leaving directory `/proj/llvm/llvm-test-1/External/SPEC/ > CFP2000/173.applu' > make[4]: Entering directory `/proj/llvm/llvm-test-1/External/SPEC/ > CFP2000/178.galgel' > /usr/bin/f95 -w -S -O2 /opt/spec/CPU2000v1.3.1/benchspec// > CFP2000/178.galgel/src/modules.f90

On 20 Mar 2007, at 15:45, Jeff Cohen wrote: > Duncan Sands wrote: >>> If that fails, I will build a front-end using ANTLR [http:// >>> antlr.org] a parser generator with which I am familiar and for >>> which a FORTRAN grammar is already available (targeting an >>> obsolete version of ANTLR, but it should not be too difficult to >>> update).

Chris Lattner wrote: > On Fri, 14 Jul 2006, Kenneth Hoste wrote: >> Besides that, I can probably rely on the expierence of some people on >> this mailinglist? > > You can always ask, but realize you are at the mercy of people's > goodwill, so you can't count on anything. In practice, we try to help, > but are often very busy. I understand, but any help I

Hello LLVM-people, I've been trying (on and off) to compile the _full_ SPEC CPU2000 benchmark suite to LLVM bytecode. The biggest problem I'm facing is the Fortran benchmarks, for which some partial support is already available it seems (using f2c). Unfortunately the f2c compiler only allows the translation of Fortran-77 programs to C code (which is then compiled using llvm-gcc).

On 01 Sep 2006, at 10:05, Kenneth Hoste wrote: > >> >>> Also, it is possible to tell make only to compile benchmark X? How >>> can I >>> enforce this? >> >> Go into the directory for that benchmark, then run 'make' or >> whatever. > I tried tom compile each of the SPEC CPU2000 benchmarks using the make command is each respective

John Criswell wrote: > Okay. As Rob has already said, it sounds like you want to write an LLVM > pass that adds global variables and instructions to a program. So, to > state it explicitly, you want to: > > 1) Compile the program that you want to instrument to LLVM bytecode > using llvm-gcc. > 2) Use an LLVM pass that you write to instrument the program. > 3) Use

Hello, Some problems were solved, new ones arised... Getting closer though... The fixes for the previous problems are at the bottom of this email, bug reports will be submitted when all problems are solved. +++ New/remaining problems +++ Currently, 9/26 benchmarks compile and run succesfully. One (fma3d) still has a f95 related problem (see below). The other 16 are divided into two groups: