On Sep 27 2012, Eugene Loh wrote:
Good discussion, but as far as my specific issue goes, it looks like
it's some peculiar interaction between different compiler versions. I'm
asking some experts.
Module incompatibility is a common problem, and the solution is NOT to
put a hack into the conf
On 9/27/2012 11:31 AM, N.M. Maclaren wrote:
On Sep 27 2012, Jeff Squyres (jsquyres) wrote:
..."that obscene hack"...
...configure mechanism...
Good discussion, but as far as my specific issue goes, it looks like
it's some peculiar interaction between different compiler versions. I'm
asking s
On Sep 27 2012, Jeff Squyres (jsquyres) wrote:
Fwiw, we have put in many hours of engineering to "that obscene hack"
*because* compilers all have differing degrees of compatibility suck.
It's going to be years before compilers fully support f08, for example,
so we have no choice but to test f
Fwiw, we have put in many hours of engineering to "that obscene hack" *because*
compilers all have differing degrees of compatibility suck. It's going to be
years before compilers fully support f08, for example, so we have no choice but
to test for various compiler characteristics at configure t
On Sep 27 2012, Jeff Squyres wrote:
On Sep 27, 2012, at 7:30 AM, Paul Hargrove wrote:
PUBLIC should be a standard part of F95 (no configure probe required).
Good.
However, the presence of "OMPI_PRIVATE" suggests you already have a
configure probe for the "PRIVATE" keyword.
Yes, we do, bec
On Wed, Sep 26, 2012 at 10:56 PM, Jeff Squyres wrote:
[...]
> > However, the presence of "OMPI_PRIVATE" suggests you already have a
> configure probe for the "PRIVATE" keyword.
>
> Yes, we do, because not all compilers support it (yet?).
>
Then I'd guess you'll need to probe for "PUBLIC" too.
S
On Sep 27, 2012, at 7:30 AM, Paul Hargrove wrote:
> Unless I am missing something here the desired incantation is either "PUBLIC"
> to make an entire module's contents accessible, or "PUBLIC :: [component]"
> for individual control.
I'm going to leave this to Craig to figure out. I know enough
Unless I am missing something here the desired incantation is either
"PUBLIC" to make an entire module's contents accessible, or "PUBLIC ::
[component]" for individual control.
PUBLIC should be a standard part of F95 (no configure probe required).
However, the presence of "OMPI_PRIVATE" suggests y
Craig: Can you reply to Eugene's question? I *assume* the answer is "no",
since we don't need it for any other compilers. Is there an optional "public"
directive that we can use?
Eugene: can you see if your compiler supports an optional "public" kind of
directive? We could discover this dire
The ibm tests aren't building for me. One of the issues is
mprobe_usempif08.f90 trying to access status%MPI_SOURCE and
status%MPI_TAG. I assume this is supposed to work, but it doesn't.
E.g., trunk with Oracle Studio compilers:
% cat a.f90
use mpi_f08
type(MPI_Status) status
write(6,*
10 matches
Mail list logo
