Displaying 4 results from an estimated 4 matches for "ccgcqxys".
2006 Sep 01
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
...lgel, equake, lucas, gcc, gap, facerec,
sixtrack, wupwise, mgrid, applu, apsi
Since these include both SPECfp and SPECint benchmarks, this has
nothing todo with f95.
*** 2) *** Undefined references
With 3 benchmarks (vpr, crafty and eon), I'm getting similar
undefined references:
/tmp/ccGCQxYs.o(.text+0x76b2): In function `init_chan':
175.vpr.cbe.c: undefined reference to `ltmp_6791_156'
/tmp/ccGCQxYs.o(.text+0x76cb):175.vpr.cbe.c: undefined reference to
`ltmp_6792_156'
/tmp/ccGCQxYs.o(.text+0x76f1):175.vpr.cbe.c: undefined reference to
`ltmp_6793_157'
/tmp/ccGCQxYs...
2006 Sep 01
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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
2006 Sep 01
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
...sixtrack, wupwise, mgrid, applu, apsi
>
> Since these include both SPECfp and SPECint benchmarks, this has
> nothing todo with f95.
>
> *** 2) *** Undefined references
>
> With 3 benchmarks (vpr, crafty and eon), I'm getting similar
> undefined references:
>
> /tmp/ccGCQxYs.o(.text+0x76b2): In function `init_chan':
> 175.vpr.cbe.c: undefined reference to `ltmp_6791_156'
> /tmp/ccGCQxYs.o(.text+0x76cb):175.vpr.cbe.c: undefined reference to
> `ltmp_6792_156'
> /tmp/ccGCQxYs.o(.text+0x76f1):175.vpr.cbe.c: undefined reference to
> `ltmp_6793_157...
2006 Sep 01
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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
>>