amber-developers: amber9-pathscale issue

From: Andreas Svrcek-Seiler <>
Date: Tue, 28 Mar 2006 03:16:36 -0700

> 5.
> f90 -c -O2 -free -o qm2_dftb_dispersionread.o
> write(6,'(A,3X,A)'), '|','DISP.INP'
> ^
> "_qm2_dftb_dispersionread.f", Line = 102, Column = 26: ERROR: Unexpected
> "operand" was expected but found ",".
...This sun issue was also a patscale issue that I would have reported.
More important: The most current Pathscale compiler (ver. 2.3.1)
gives an ICE when compiling "force.f" with "-O3":
  pathf90 -c -O3 -intrinsic=PGI -intrinsic=fdate -freeform -o force.PIMD.o
Signal: Segmentation fault in Loop Nest Optimizer phase.
Error: Signal Segmentation fault in phase Loop Nest Optimizer --
processing aborted
pathf90 INTERNAL ERROR: /scr/orgon/svrci/PATHSC.2.3.1/lib/2.3.1/be died
due to signal 4
pathf90 ERROR: core dumped
This is pathscale's problem, but sooner or later someone who will have
spent lots of $ on amber9 and the compiler will copmplaine about that.
(solution: compile just force.f with "-O2").

Received on Wed Apr 05 2006 - 23:49:33 PDT
Custom Search