🚀 go-pugleaf

Archive-name: auto/comp.parallel/New-Release-of-iPSC-DASH-library-and-some-Fortran-Questions

=========== 
NEW RELEASE 
===========

A new release of the  iPSC/DASH  library  is  now  available  via
anonymous   FTP  from  mojave.stanford.edu  under  the  directory
/pub/dash-msg-library.

By default, the library will  run  with  64  virtual  processors.
(See Makefile on how to change default value or to map virtual to
physical processors.)  Please be warned that each  one   of   the
processes will create a  mmap  on  your  /tmp partition.   So, if
you do not have too much disk space, try  not  to  run  too  many
processes.   As  you  probably  know,  mmap is not known for good
behavior.  By being too ambitious you will only end up  rebooting
your machine.

A FORTRAN-to-C wrapper has been  included  in  our latest distri-
bution  of  the  iPSC/DASH  library.    See  the  included sample
makefile "makef77" for linking and loading information.  However,
certain  functions  supported  in  the  C  distribution  are  NOT
supported in the  FORTRAN  version  until  further  notification.
These  include:  hsend,  hrecv,  forflush, cwrite  and  cread.

In addition, the FORTRAN library has been integrated successfully
with  FORTNET,  a  parallel  computing  utility developed  by the
Daresbury Laboratory  of  the  British  Science  and  Engineering
Research Council (SERC).  FORTNET  in  turn  interfaces with PAR-
LANCE, which represents a wealth of machine-independent  parallel
numerical algorithms  from  major European research institutions.
Please  contact  Dr.  Robert  J.  Allan  of  the  SERC  Daresbury
Laboratory  (rja@cxa.dl.ac.uk) directly for licensing information
on FORTNET and PARLANCE.

We have received a few complaints about  compiler  compatibility.
As  a  result,  a binary copy of the library has been enclosed in
the current distribution.  Please download the  files  in  binary
mode to ensure 100% compatibility.

We are interested in hearing from you if  you  have  successfully
run applications on any machine outside of Stanford or NASA Ames.

Thanks very much.



======================================== 
FORTRAN QUESTIONS THAT WE NEED HELP WITH
========================================

(1) Can any FORTRAN expert out there teach us how  to  pass  that
void (*func)() to hsend or hrecv in C?   We can wrap a void *func
pointer from FORTRAN to C and then recast it.  But we aren't sure
if  FORTRAN  is  actually  passing a pointer when it is trying to
pass a function as an argument to a subroutine.

(2) Can the folks from Intel or anyone else send us some informa-
tion about the new OSF/860 specifications?