similar to: [LLVMdev] Google SOC - Idea

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

Getting the front end for Fortran finished is definitely something I would be interested in working on. I will draft up a little proposal and send it out to this list. -Scott On 3/19/07, Kenneth Hoste <kenneth.hoste at ugent.be> wrote: > Hi Scott, > > On 18 Mar 2007, at 04:22, Scott Fortmann-Roe wrote: > > > Hi, > > > > I noticed that LLVM had signed up as a

Hi, Here is a rough draft of the application -- a FORTRAN front-end to LLVM. In accordance with the summer of code specifications it is split into two portions: the abstract which describes the project, and the details description which describes me and how I plan to complete the project. It's a little long, (but about half the max length the application directions specify). Would someone be

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). >> > > Bad plan. I doubt you can build a serious fortran

Hi Scott, I'm currently porting the Ada gcc front-end to LLVM. This is similar to what you want to do, so here are some comments from the trenches... > I plan on first attempting to implement the FORTRAN front-end by > co-opting the GCC FORTRAN parser. Good plan. However the Fortran front-end that comes with gcc 4.0 is known to be weak (llvm-gcc is based on gcc 4.0). That's

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 >>

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

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 > enforce this? Go into the directory for that benchmark, then run 'make' or whatever. -Chris --

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 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

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.

Hi All, Thank you for all the excellent pieces of advice I got in response to the draft application I sent out. I have incorporated all (I think) of the suggestions into the application and it's much improved. Here is the updated version. Please don't force yourself to read through it again if you don't want to. I'll submit this version with any suggestions I receive on the 23rd.

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:

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

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).

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

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 := /work/NAG_f95/bin/f95 > F95_INC := /work/NAG_f95/lib > F95_LIB := /work/NAG_f95/lib > > Looks

On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> It doesn't to me. If you set F95_DIR to /work/NAG_f95 things will >> probably work much better for you. > > No, that doesn't seem to be the problem. If I provide the additional > --with-f95 option with the correct directory to configure, > I still get the same errors (although it mentions /work/NAG_f95/lib/ >