similar to: [LLVMdev] LLVM bytecode simulator/emulator?

On Wed, 12 Jul 2006, Kenneth Hoste wrote: > 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

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 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 programs to fail in it. > > What do you mean

Chris Lattner wrote: > On Thu, 13 Jul 2006, Kenneth Hoste wrote: >> After browsing through the docs, at a first glance I think I should >> write a plugin for the 'analyze' tool. I think >> http://llvm.org/docs/WritingAnLLVMPass.html is where I should start from. >> The only problem I see now is that there doesn't seem to be a way to >> get

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

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 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. > What is the best way to start such an ambitious project? Do I > just check

On Thu, 13 Jul 2006, Kenneth Hoste wrote: > After browsing through the docs, at a first glance I think I should write a > plugin for the 'analyze' tool. I think > http://llvm.org/docs/WritingAnLLVMPass.html is where I should start from. > The only problem I see now is that there doesn't seem to be a way to get > information on a single instruction while being able to

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

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

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

Kenneth Hoste wrote: > 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

Kenneth Hoste wrote: > Chris Lattner wrote: >> On Thu, 13 Jul 2006, Kenneth Hoste wrote: >>> After browsing through the docs, at a first glance I think I should >>> write a plugin for the 'analyze' tool. I think >>> http://llvm.org/docs/WritingAnLLVMPass.html is where I should start >>> from. >>> The only problem I see now is that

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

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

Hi Chris, > > 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 --with-spec2000=/work/SPEC_CPU2000_1.3_src/benchspec -- without-f2c --with-f95-bin=/work/NAG_f95/bin --with-f95-lib=/work/