Opened 6 years ago

Closed 5 years ago

Last modified 3 years ago

#1411 closed Bug (fixed)

LIM3 compiler error with gfortran (gcc48) in limdiahsb

Reported by: clevy Owned by: vancop
Priority: highest Milestone: 2015 release-3.6
Component: LIM3 Version: trunk
Severity: Keywords: 2015 LIM* release-3.6
Cc:

Description

In the trunk revision 4862, running the SETTE tests when using gfortran compiler (gcc48), 
/Users/clairelevy/Documents/WORK/FORORCA1/NEMOGCM/CONFIG/ORCA2LIM3_LONG/BLD/ppsrc/nemo/limdiahsb.f90:88.26:

  zinda = MAX( 0.d0 , SIGN( 1.d0 , glob_sum( area(:,:) * tms(:,:) ) - epsi0
    1

Error: Generic function 'sign' at (1) is not consistent with a specific intrinsic interface
/Users/clairelevy/Documents/WORK/FORORCA1/NEMOGCM/CONFIG/ORCA2LIM3_LONG/BLD/ppsrc/nemo/limdiahsb.f90:164.26:

  zindb = MAX( 0.d0 , SIGN( 1.d0 , zbg_ivo - epsi06 ) )
    1

Error: Generic function 'sign' at (1) is not consistent with a specific intrinsic interface

In the trunk revision 4862, when using gfortran compiler,
/Users/clairelevy/Documents/WORK/FORORCA1/NEMOGCM/CONFIG/ORCA2LIM3_LONG/BLD/ppsrc/nemo/limdiahsb.f90:88.26:

zinda = MAX( 0.d0 , SIGN( 1.d0 , glob_sum( area(:,:) * tms(:,:) ) - epsi0

1

Error: Generic function 'sign' at (1) is not consistent with a specific intrinsic interface
/Users/clairelevy/Documents/WORK/FORORCA1/NEMOGCM/CONFIG/ORCA2LIM3_LONG/BLD/ppsrc/nemo/limdiahsb.f90:164.26:

zindb = MAX( 0.d0 , SIGN( 1.d0 , zbg_ivo - epsi06 ) )

1

Error: Generic function 'sign' at (1) is not consistent with a specific intrinsic interface

Commit History (0)

(No commits)

Change History (8)

comment:1 Changed 5 years ago by clevy

  • Milestone set to 2015 nemo_v3_6_STABLE
  • Owner changed from NEMO team to vancop

comment:2 Changed 5 years ago by timgraham

I think this has been fixed as part of the 2014 merge. The above line now reads:

zinda = MAX( 0._wp , SIGN( 1._wp , glob_sum( area(:,:) * tms(:,:) ) - epsi0

I think the error might be due to the use of 1.d0 in the call to SIGN. Is anyone able to test this easily with the gfortran compiler to see if we can close the ticket?

comment:3 Changed 5 years ago by clem

  • Resolution set to fixed
  • Status changed from new to closed

yes, I tested it and it is working with gfortran 4.8.2 (ubuntu OS)

comment:4 Changed 4 years ago by nicolasmartin

  • Keywords 2015 nemo_v3_6* added

comment:5 Changed 3 years ago by nemo

  • Keywords release-3.6* added; nemo_v3_6* removed

comment:6 Changed 3 years ago by nemo

  • Keywords LIM* added

comment:7 Changed 3 years ago by nemo

  • Keywords release-3.6 added

comment:8 Changed 3 years ago by nemo

  • Keywords release-3.6* removed
Note: See TracTickets for help on using tickets.