Hi Jeff,
Thanks so much for replying to my emails! Yes, the problem with the
BOOL was with a define in our code, so LAM/MPI was not at fault there.
More about DOUBLE_COMPLEX: is it valid or not to do
MPI_Send(&cplx,...MPI_DOULE_COMPLEX,...), where cplx is complex<double>?
Furthermore, is it valid or not to do the same as above, but with cplx
being a struct {double re,double im};(in LAM?) It wasn't very clear
from your reply, except that MPI wasn't very specific on that point.
Thanks again.
Kevin
> From: Jeff Squyres <jsquyres_at_[hidden]>
> To: General LAM/MPI mailing list <lam_at_[hidden]>
> Subject: Re: LAM: constants.h and other things
> Date: 16 Sep 2004 06:27:30 -0400
>
> On Sep 15, 2004, at 12:50 PM, Kevin Kuo wrote:
>
> > I have LAM/MPI 7.0.6 running on a small linux cluster. When I tried to
> > compile a c++ project I get the following errors in constant.h
> >
> > /usr/local/lam/include/mpi2cxx/constants.h:128: redeclaration of C++
> > built-in
> > type `int'
> > /usr/local/lam/include/mpi2cxx/constants.h:129: declaration does not
> > declare
> > anything
> >
> > my g++ version is "3.2 20020903 (Red Hat Linux 8.0 3.2-7)"
> >
> > here is what constants.h says:
> >
> > 127 // c++ types
> > 128 extern const Datatype BOOL;
>
> Can you run this through the preparser can see what the output is?
> i.e., perhaps "BOOL" was defined to "int" somewhere...?
>
> > 129 extern const Datatype COMPLEX;
> > 130 extern const Datatype DOUBLE_COMPLEX;
> > 131 extern const Datatype LONG_DOUBLE_COMPLEX;
> >
> > so what's wrong here? If I put a #if 0...#endif block around these
> > lines, it will continue to compile, but why was there an error in the
> > first place?
> >
> > Secondly, I have access to some C/C++ code that uses MPI_DOUBLE_COMPLEX
> > data type in the MPI_Datatype argument for Send, recv, etc. This type
> > is suppose to be only Fortran only? Mpich 1.2.6 allows me to compile
> > it, but breaks on the offending line when executing, while lam-7.0.6
> > does not allow me to compile it, saying that MPI_DOUBLE_COMPLEX is
> > undefined. So which implementation has it correct? I imagine LAM's
> > got
> > it correct because C doesn't have any support for COMPLEX numbers and
> > the users have to use MPI's functions to generate derived types for the
> > Complex structures.
>
> Technically, the MPI standard doesn't say that you have to implement
> MPI_DOUBLE_COMPLEX in C -- it is supposed to be a fortran type
> (analogously, MPI::DOUBLE_COMPLEX is C++ only). For example, there's
> also no MPI_INTEGER available in C (the fortran integer) -- there's
> only MPI_INT.
>
> You're correct that C99 defines a complex type in C, but that type
> didn't exist when the MPI standard was written (1994, 1996). :-)
>
> > Thirdly, if I generate a derived type for a structure (call it Complex)
> > in C, and I want to send an array of these Complex structures, is the
> > count field the number the number of elements in the array (using
> > MPI_Type_vector), or should the derived type be generated for the array
> > of Complex objects and in that case the count is 1? Thanks for any
> > feedback.
>
> In MPI, "count" refers to the number of datatype instances that you
> want to send. So if you make a datatype representing a complex, if you
> want to send 3 of those complex instances, your count would be 3.
>
> Make sense?
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
>
>
> ----
>
> From: Matthew Golabiewski <m.golabiewski_at_[hidden]>
> To: lam_at_[hidden]
> Subject: LAM: Benchmarking Question.
> Date: 16 Sep 2004 05:09:04 -0700
>
> ----
>
> From: Jeff Squyres <jsquyres_at_[hidden]>
> To: General LAM/MPI mailing list <lam_at_[hidden]>
> Subject: Re: LAM: Problems with Lam 7.1b22
> Date: 16 Sep 2004 08:25:13 -0400
>
> LAM 7.1b24, built with Libtool 1.5.8 is now on the web site. See if
> that fixes the linker problem.
>
> http://www.lam-mpi.org/beta/
>
>
> On Sep 16, 2004, at 4:36 AM, Jeff Squyres wrote:
>
> > On Sep 15, 2004, at 8:30 AM, Ralf Wildenhues wrote:
> >
> >>> pgf77-Warning-Unknown switch: --export-dynamic
> >>
> >> This /might/ be a libtool problem. You could try to find out by
> >> manually setting the correct value for export_dynamic_flag_spec in
> >> $builddir/libtool after running configure. Then rebuild (possibly
> >> after
> >> a `make clean'). If this solves this problem, please carry this over
> >> to
> >> the libtool mailing list including any details you've found out.
> >>
> >> Is lam using a recent version of libtool?
> >
> > LAM 7.1bx is 1.5.6. I see that there is a 1.5.8 available; I can make
> > a new beta with 1.5.8 and see if that helps.
> >
> > I still need the information about running with valgrind and whatnot
> > to see if we have a real seg fault in there, however.
> >
> > --
> > {+} Jeff Squyres
> > {+} jsquyres_at_[hidden]
> > {+} http://www.lam-mpi.org/
> >
> > _______________________________________________
> > This list is archived at http://www.lam-mpi.org/MailArchives/lam/
> >
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
>
>
> ----
>
> From: Matthew Golabiewski <m.golabiewski_at_[hidden]>
> To: General LAM/MPI mailing list <lam_at_[hidden]>
> Subject: LAM: RE: Benchmarking Question.
> Date: 16 Sep 2004 05:28:31 -0700
>
> I know this has probably been asked before and I am sort of a newbie.
> I was wonder what tools are available for benchmarking and LAM-MPI
> cluster.
> What Tools and programs do you recommend on the Linux platform?
>
> Thanks,
> Matthew Golabiewski.
>
> Ps. Mistake made so I am reposting it as a Reply
>
|
