This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Eugene Loh wrote:
> Sangamesh B wrote:
>> The job is run on 2 nodes - 8 cores.
>> OpenMPI - 25 m 39 s.
>> MPICH2 - 15 m 53 s.
> I don't understand MPICH very well, but it seemed as though some of
> the flags used in building MPICH are supposed to be added in
> automatically to the mpicc/etc compiler wrappers.
Again, this may not apply to your case, but I found out some more
details on my theory.
If you build MPICH2 like this:
% configure CFLAGS=-O2
then when you use "mpicc" to build your application, you automatically
get that optimization flag built in.
What had confused me was that I tried confirming the theory by building
MPICH2 like this:
% configure --enable-fast
That does *NOT* up the mpicc optimization level (despite their