Thank you all for the replies.
Certainly optimization flags can be useful to address differences between
compilers, etc. And differences in MPI_ALLREDUCE are appreciated as possible.
But I don't think either is quite relevant because:
- It was exact same compiler, with identical compilation fl
I've not been following closely. How do you know you're using the
identical compilation flags? Are you saying you specify the same flags
to "mpicc" (or whatever) or are you confirming that the back-end
compiler is seeing the same flags? The MPI compiler wrapper (mpicc, et
al.) can add flags.
Am 20.09.2011 um 16:50 schrieb Blosch, Edwin L:
> Thank you all for the replies.
>
> Certainly optimization flags can be useful to address differences between
> compilers, etc. And differences in MPI_ALLREDUCE are appreciated as possible.
> But I don't think either is quite relevant because:
>
On 9/20/2011 10:50 AM, Blosch, Edwin L wrote:
It appears to be a side effect of linkage that is able to change a compute-only
routine's answers.
I have assumed that max/sqrt/tiny/abs might be replaced, but some other kind of
corruption may be going on.
Those intrinsics have direct instruct
Subject: Re: [OMPI users] EXTERNAL: Re: How could OpenMPI (or MVAPICH) affect
floating-point results?
On 9/20/2011 10:50 AM, Blosch, Edwin L wrote:
> It appears to be a side effect of linkage that is able to change a
> compute-only routine's answers.
>
> I have assumed that max/sqrt/
-mP1OPT_source_file_name=../../../code/src/main/main.f90
../../../code/src/main/main.f90
../../../code/src/main/main.f90
-Original Message-
From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On Behalf
Of Eugene Loh
Sent: Tuesday, September 20, 2011 10:08 AM
To:
