search for: tomcatv

...e to link with gcc, since llvm still wants to link against the 64-bit crt*.o and libs. Maybe it is easier to just have two separate builds. That said, my simple dynamically linked hello world executed fine (ie, it was able to call into libc.so just fine), as well as an old C version of the SPEC97 tomcatv benchmark I have laying around. So it seems both 32-bit and 64-bit can call into shared libs. Not to say I haven't seen some code gen warts (using -O3). :) >From hello.s: main: mflr 0 stw 31, -4(1) stw 0, 4(1) stwu 1, -16(1) lis 3, .Lstr at ha...

...code of an executing program. Specifically, I want to be able to insert NOPs (into functions and loops) at compile time that I patch into calls to subroutines at runtime. My questions are: A. The testresults at http://llvm.cs.uiuc.edu/testresults/X86/ show that several benchmarks (swim, applu, tomcatv, su2cor...) in the Spec CFP 2000 and 95 suites failed when run under the JIT. Why did they fail and what are the limitations in running Spec benchmarks? B. Is what I am suggesting in 3 possible in LLVM? C. Has anyone here used both LLVM and Intel's PIN? If so, can you comment on the drawba...

On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > By default it should build for > whatever the current host is (no special flags required). To > specifically build for something else, use: > -ccc-host-triple powerpc64-unknown-linux-gnu > or > -ccc-host-triple powerpc-unknown-linux-gnu So LLVM isn't biarch capable? Meaning one LLVM compiler cannot generate both

...NOPs and then write over them? Can't you just replace calls to functions with calls to new functions that in turn call whatever subroutines you like? > My questions are: > > A. The testresults at http://llvm.cs.uiuc.edu/testresults/X86/ show that > several benchmarks (swim, applu, tomcatv, su2cor...) in the Spec CFP 2000 > and 95 suites failed when run under the JIT. Why did they fail and what > are the limitations in running Spec benchmarks? I'm not sure why these don't run in the JIT, actually. They should. (Anyone?) > B. Is what I am suggesting in 3 possible i...

...> still wants to link against the 64-bit crt*.o and libs. Maybe it is > easier to just have two separate builds. > > That said, my simple dynamically linked hello world executed fine > (ie, it was able to call into libc.so just fine), as well as an > old C version of the SPEC97 tomcatv benchmark I have laying around. > So it seems both 32-bit and 64-bit can call into shared libs. > > Not to say I haven't seen some code gen warts (using -O3). :) > > From hello.s: > > main: > mflr 0 > stw 31, -4(1) > stw 0, 4(1) >...

On Tue, 01 May 2012 17:23:07 -0500 Peter Bergner <bergner at vnet.ibm.com> wrote: > On Tue, 2012-05-01 at 16:06 -0500, Hal Finkel wrote: > > LLVM/clang now will build in the normal way (./configure; make > > install) on PPC (you'll need at least the 3.1 release candidate (or > > trunk)). I generally build on my PPC64 hosts with: > > make ENABLE_OPTIMIZED=1