search for: maxcontin

...ch are reported subsequently. Affected benchmarks: galgel, facerec, sixtrack *** BEAM (fma3d) There seem to be some issues with the fma3d benchmark, when translating from Fortran to C: f95 -w -S -O2 <path>/SPEC_CPU2000_1.3_src/benchspec/CFP2000/191.fma3d/ src/beam.f90 -o beam.c -dusty -maxcontin=69 Error: <path>/SPEC_CPU2000_1.3_src/benchspec/CFP2000/191.fma3d/src/ beam.f 90: Binding label 'beam_' of COMMON/BEAM/ matches module BEAM_ [f95 error termination] Also a f95-related issue I'd guess. Affected benchmarks: fma3d. *** greetings, Kenneth -- Statistics are li...

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

...y, here's how the NAG problems got fixed. > *** BEAM (fma3d) > > There seem to be some issues with the fma3d benchmark, when > translating from Fortran to C: > > f95 -w -S -O2 <path>/SPEC_CPU2000_1.3_src/benchspec/CFP2000/191.fma3d/ > src/beam.f90 -o beam.c -dusty -maxcontin=69 > Error: <path>/SPEC_CPU2000_1.3_src/benchspec/CFP2000/191.fma3d/src/ > beam.f > 90: Binding label 'beam_' of COMMON/BEAM/ matches module BEAM_ > [f95 error termination] > > Also a f95-related issue I'd guess. > > Affected benchmarks: fma3d. This is yet...

...got > fixed. > >> *** BEAM (fma3d) >> >> There seem to be some issues with the fma3d benchmark, when >> translating from Fortran to C: >> >> f95 -w -S -O2 <path>/SPEC_CPU2000_1.3_src/benchspec/CFP2000/191.fma3d/ >> src/beam.f90 -o beam.c -dusty -maxcontin=69 >> Error: <path>/SPEC_CPU2000_1.3_src/benchspec/CFP2000/191.fma3d/src/ >> beam.f >> 90: Binding label 'beam_' of COMMON/BEAM/ matches module BEAM_ >> [f95 error termination] >> >> Also a f95-related issue I'd guess. >> >> Affected...