--- MITgcm/eesupp/inc/BARRIER.h 2001/09/21 03:54:35 1.4 +++ MITgcm/eesupp/inc/BARRIER.h 2004/03/27 03:51:50 1.5 @@ -1,4 +1,4 @@ -C $Header: /home/ubuntu/mnt/e9_copy/MITgcm/eesupp/inc/BARRIER.h,v 1.4 2001/09/21 03:54:35 cnh Exp $ +C $Header: /home/ubuntu/mnt/e9_copy/MITgcm/eesupp/inc/BARRIER.h,v 1.5 2004/03/27 03:51:50 edhill Exp $ C $Name: $ CBOP C !ROUTINE: BARRIER.h @@ -22,7 +22,7 @@ C | are good, sometimes they are lousy. C | The barrier mechanism is used as follows C | 1. In the single-threaded part of the code -C | CALL FBAR_INIT +C | CALL FBAR\_INIT C | on CRAY, NEC this routine does nothing C | on T3E there is no single-threaded code C | but there may be barrier initialisation - @@ -30,7 +30,7 @@ C | 2. When we need to synchronize everybody just C | CALL FBAR( myThid ) C | where myThid is myThreadId -C | on CRAY, NEC FBAR will just do C$DIR BARRIER +C | on CRAY, NEC FBAR will just do C\$DIR BARRIER C | or the like. C | on T3E FBAR does CALL BARRIER(...) or something C | need to check this.