On 2012-03-16, at 11:52 PM, case wrote:
> On Fri, Mar 16, 2012, Romelia Salomon wrote:
>>
>> the intel compiler 10.1
>> Example of errors with intel
>>
>> ifort -c -DBINTRAJ \
>> \
>> -ip -O3 -axSTPW -FR
>> -I/server-home2/romelia/amber-mine/include
>> -I/server-home2/romelia/amber-mine/include \
>> -o rism3d_fft.o rism3d_fft.F90
>> fortcom: Error: rism3d_fft.F90, line 319: A pointer dummy argument with the
>> INTENT(IN) attribute shall not appear as an actual argument if the
>> associated dummy
>> argument has the INTENT(OUT) or INTENT(INOUT) attribute. [INR]
>> inr(:,1),this%grid%ngk(3:1:-1),1,product(this%grid%ngk),&
>> ---------^
>
> I can confirm this, although later intel compilers seem fine. The errors
> go away if you remove the "intent" attributes from inr, outr and datar in
> rism3d_fft.F90. Since what was removed was "intent(inout)", maybe that is OK.
>
> Doing that doesn't seem to do any harm...rism tests still pass. I guess
> this gets passed on to Tyler....
I've pushed a fix. As Dave said, removing intent(inout) does the trick and has the same meaning. It turns out this is an Intel 10.1 compiler bug.
Tyler
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sat Mar 17 2012 - 09:30:04 PDT
