Re: [OMPI users] linker library file for both fortran and c compilers
Am 08.09.2013 um 00:44 schrieb basma a.azeem:
> sorry for the trivial question
> i am new to open mpi and parallel computing
>
> i installed openmpi-1.6.1 on my pc which has an ubuntu 12.10
> also i have nas parallel benchmark , i need to edit the NPB make file
> "make.def"
What about using:
F77 = mpif77
resp.
CC = mpicc
which should supply the paths and names automatically.
-- Reuti
> i need to know what is the linker library file for both fortran and c
> compilers and where i can find them in the build folder ( i think i should
> find them in lib folder )
> it is F_LIB and C_LIB that are required
> this is the NPB make file:
>
>
> #---
> #
> #SITE- AND/OR PLATFORM-SPECIFIC DEFINITIONS.
> #
> #---
>
> #---
> # Items in this file will need to be changed for each platform.
> #---
>
> #---
> # Parallel Fortran:
> #
> # For CG, EP, FT, MG, LU, SP, BT and UA, which are in Fortran, the following
> # must be defined:
> #
> # F77- Fortran compiler
> # FFLAGS - Fortran compilation arguments
> # F_INC - any -I arguments required for compiling Fortran
> # FLINK - Fortran linker
> # FLINKFLAGS - Fortran linker arguments
> # F_LIB - any -L and -l arguments required for linking Fortran
> #
> # compilations are done with $(F77) $(F_INC) $(FFLAGS) or
> #$(F77) $(FFLAGS)
> # linking is done with $(FLINK) $(F_LIB) $(FLINKFLAGS)
> #---
>
> #---
> # This is the fortran compiler used for Fortran programs
> #---
> F77 = f77
> # This links fortran programs; usually the same as ${F77}
> FLINK= $(F77)
>
> #---
> # These macros are passed to the linker
> #---
> F_LIB =
>
> #---
> # These macros are passed to the compiler
> #---
> F_INC =
>
> #---
> # Global *compile time* flags for Fortran programs
> #---
> FFLAGS= -O
>
> #---
> # Global *link time* flags. Flags for increasing maximum executable
> # size usually go here.
> #---
> FLINKFLAGS = -O
>
>
> #---
> # Parallel C:
> #
> # For IS and DC, which are in C, the following must be defined:
> #
> # CC - C compiler
> # CFLAGS - C compilation arguments
> # C_INC - any -I arguments required for compiling C
> # CLINK - C linker
> # CLINKFLAGS - C linker flags
> # C_LIB - any -L and -l arguments required for linking C
> #
> # compilations are done with $(CC) $(C_INC) $(CFLAGS) or
> #$(CC) $(CFLAGS)
> # linking is done with $(CLINK) $(C_LIB) $(CLINKFLAGS)
> #---
>
> #---
> # This is the C compiler used for C programs
> #---
> CC = cc
> # This links C programs; usually the same as ${CC}
> CLINK= $(CC)
>
> #---
> # These macros are passed to the linker
> #---
> C_LIB = -lm
>
> #---
> # These macros are passed to the compiler
> #---
> C_INC =
>
> #---
> # Global *compile time* flags for C programs
> # DC inspects the following flags (preceded by "-D"):
> #
> # IN_CORE - computes all views and checksums in main memory (if there is
> # enough memory)
> #
> # VIEW_FILE_OUTPUT - forces DC to write the generated views to disk
> #
> # OPTIMIZATION - turns on some nonstandard DC optimizations
> #
> # _FILE_OFFSET_BITS=64
> # _LARGEFIL
[OMPI users] OMPI_LIST_GROW keeps allocating memory
Hi All, using ompi 1.4.5 or 1.6.5 for that matter, I came across an interesting thing when an MPI function is called from in a recusivly called subroutine (Fortran Interface) the MPI_ALLREDUCE function allocates memory in the OMPI_LIST_GROW functions. It does this indefinitly. In our case OMPI allocated 100GB. is there a method to limit this behaviour ? thanks Max
Re: [OMPI users] OMPI_LIST_GROW keeps allocating memory
This is not supposed to happen. Can you please post an example highlighting this behavior? George. On Sep 8, 2013, at 14:51 , Max Staufer wrote: > Hi All, > > using ompi 1.4.5 or 1.6.5 for that matter, I came across an > interesting thing > > when an MPI function is called from in a recusivly called subroutine > (Fortran Interface) > the MPI_ALLREDUCE function allocates memory in the OMPI_LIST_GROW functions. > > It does this indefinitly. In our case OMPI allocated 100GB. > > is there a method to limit this behaviour ? > > thanks > > Max > > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] OMPI_LIST_GROW keeps allocating memory
I will post a small example for testing. It is interesting to note though that this happens only when MPI_ALLREDUCE is called in a recursive kind of way. Is there a possibility to limit the OMPI_free_list groth, via an --mca parameter ? List-Post: users@lists.open-mpi.org Date: Sun, 08 Sep 2013 14:51:44 +0200 From: Max Staufer To: us...@open-mpi.org Subject: [OMPI users] OMPI_LIST_GROW keeps allocating memory Message-ID: <522c72e0.9000...@gmx.net> Content-Type: text/plain; charset=ISO-8859-15 Hi All, using ompi 1.4.5 or 1.6.5 for that matter, I came across an interesting thing when an MPI function is called from in a recusivly called subroutine (Fortran Interface) the MPI_ALLREDUCE function allocates memory in the OMPI_LIST_GROW functions. It does this indefinitly. In our case OMPI allocated 100GB. is there a method to limit this behaviour ? thanks Max
Re: [OMPI users] OMPI_LIST_GROW keeps allocating memory
Yes, the number of elements each freelist accepts to allocate can be bounded. However, we need to know which freelist we should act upon. What exactly you means by "MPI_ALLREDUCE is called in a recursive way"? You mean inside a loop right? George. On Sep 8, 2013, at 21:36 , Max Staufer wrote: > I will post a small example for testing. > > It is interesting to note though that this happens only > > when MPI_ALLREDUCE is called in a recursive kind of way. > > Is there a possibility to limit the OMPI_free_list groth, via an --mca > parameter ? > > > > > > > > Date: Sun, 08 Sep 2013 14:51:44 +0200 > From: Max Staufer > To: us...@open-mpi.org > Subject: [OMPI users] OMPI_LIST_GROW keeps allocating memory > Message-ID: <522c72e0.9000...@gmx.net> > Content-Type: text/plain; charset=ISO-8859-15 > > Hi All, > > using ompi 1.4.5 or 1.6.5 for that matter, I came across an > interesting thing > > when an MPI function is called from in a recusivly called subroutine > (Fortran Interface) > the MPI_ALLREDUCE function allocates memory in the OMPI_LIST_GROW functions. > > It does this indefinitly. In our case OMPI allocated 100GB. > > is there a method to limit this behaviour ? > > thanks > > Max > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
