day about where the newer PGI compilers are
hiding
> > out at LANL.
> >> I'll check this out today.
> >>
> >> Howard
> >>
> >>
> >> -Original Message-----
> >> From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of
to:devel-boun...@open-mpi.org] On Behalf Of Pritchard
> Jr., Howard
>> Sent: Friday, August 01, 2014 8:59 AM
>> To: Open MPI Developers
>> Subject: Re: [OMPI devel] openmpi-1.8.2rc2 and f08 interface built with
> PGI-14.7 causes link error
>>
>> Hi Jeff,
>>
open-mpi.org] On Behalf Of Pritchard
Jr., Howard
> Sent: Friday, August 01, 2014 8:59 AM
> To: Open MPI Developers
> Subject: Re: [OMPI devel] openmpi-1.8.2rc2 and f08 interface built with
PGI-14.7 causes link error
>
> Hi Jeff,
>
> Finally got info yesterday about where the newe
uyres
(jsquyres)
Sent: Tuesday, July 29, 2014 5:24 PM
To: Open MPI Developers List
Subject: Re: [OMPI devel] openmpi-1.8.2rc2 and f08 interface built with
PGI-14.7 causes link error
Tetsuya --
I am unable to test with the PGI compiler -- I don't have a license. I was
hoping that LANL would be ab
n MPI Developers List
Subject: Re: [OMPI devel] openmpi-1.8.2rc2 and f08 interface built with
PGI-14.7 causes link error
Tetsuya --
I am unable to test with the PGI compiler -- I don't have a license. I was
hoping that LANL would be able to test today, but I don't think they got to it
Trunk now works for me using Tetsuya's test code with both PGI-14.1 and 14.4
-Paul
On Thu, Jul 31, 2014 at 6:17 PM, Jeff Squyres (jsquyres) wrote:
> Many thanks guys, this thread was most helpful in finding the fix.
>
> Paul H. nailed 80% of it on the head in the post where he identified the
>
Paul,
the ibm test suite from the non public ompi-tests repository has several
tests for usempif08.
Cheers,
Gilles
On 2014/08/01 11:04, Paul Hargrove wrote:
> Second related issue:
>
> Can/should examples/hello_usempif08.f90 be extended to use more of the
> module such that it would have illust
Nevermind my suggestion to revise examples/hello_usempif08.f90
I've just determined that it is already sufficient to reproduce the problem.
(So now I need to see what's wrong in my testing scripts).
-Paul
On Thu, Jul 31, 2014 at 7:04 PM, Paul Hargrove wrote:
> Second related issue:
>
> Can/sho
Second related issue:
Can/should examples/hello_usempif08.f90 be extended to use more of the
module such that it would have illustrated the bug found with Tetsuya's
example code? I don't know about MTT, but my scripts for testing a
release candidate includes running "make" in the example subdir.
Related question:
If I am understanding PGI's list of fixed-TPRs (bugs) then it looks like
one (certainly not the only) difference between 13.x and 14.1 is a fix to a
problem with PROCEDURE and zero-argument subroutines. As it happens, the
configure probe for PROCEEDURE is a zero-argument subrout
Many thanks guys, this thread was most helpful in finding the fix.
Paul H. nailed 80% of it on the head in the post where he identified the
Makefile.am change. That Makefile.am change was due to three things:
1. Fixing a real bug (elsewhere in that commit)
2. My misunderstanding of how module f
Gilles,
Just as you speculate, PGI is creating a _-suffixed reference to the module
name:
$ pgf90 -c test.f90
$ nm -u test.o | grep f08
U mpi_f08_sizeof_
U mpi_f08_sizeof_mpi_sizeof_real_s_4_
You suggested the following work-around in a previous email:
$ INS
Paul,
in .../ompi/mpi/fortran/use-mpi-f08, can you create the following dumb
test program,
compile and run nm | grep f08 on the object :
$ cat foo.f90
program foo
use mpi_f08_sizeof
implicit none
real :: x
integer :: size, ierror
call MPI_Sizeof_real_s_4(x, size, ierror)
stop
end program
wi
Paul and all,
For what it's worth, with openmpi 1.8.2rc2 and the intel fortran
compiler version 14.0.3.174 :
$ nm libmpi_usempif08.so| grep -i sizeof
there is no such undefined symbol (mpi_f08_sizeof_)
as a temporary workaround, did you try to force the linker use
libforce_usempif08_internal_mo
Hi Paul,
Thank you for your investigation. I'm sure it's very
close to fix the problem although I myself can't do
that. So I must owe you something...
Please try Awamori, which is Okinawa's sake and very
good in such a hot day.
Tetsuya
> On Wed, Jul 30, 2014 at 8:53 PM, Paul Hargrove wrote:
>
On Wed, Jul 30, 2014 at 8:53 PM, Paul Hargrove wrote:
[...]
> I have a clear answer to *what* is different (below) and am next looking
> into the why/how now.
> It seems that 1.8.1 has included all dependencies into libmpi_usempif08
> while 1.8.2rc2 does not.
>
[...]
The difference appears to s
On Wed, Jul 30, 2014 at 6:20 PM, Paul Hargrove wrote:
>
> On Wed, Jul 30, 2014 at 6:15 PM, wrote:
> [...]
>
>> Strange thing is that openmpi-1.8 with PGI14.7 works fine.
>> What's the difference with openmpi-1.8 and openmpi-1.8.2rc2?
>>
> [...]
>
> Tetsuya,
>
> Now that I can reproduce the probl
On Wed, Jul 30, 2014 at 6:15 PM, wrote:
[...]
> Strange thing is that openmpi-1.8 with PGI14.7 works fine.
> What's the difference with openmpi-1.8 and openmpi-1.8.2rc2?
>
[...]
Tetsuya,
Now that I can reproduce the problem you have reported, I am building 1.8.1
with PGI14.4.
Then I may be able
Jeff,
I can now reproduce Tetsuya's original problem, using a build of 1.8.2rc2
with PGI 14.4.
$ INST/bin/mpifort ../test.f
/scratch/scratchdirs/hargrove/pgf90pdegT3bhBmEq.o: In function `.C1_283':
test.f:(.data+0x6c): undefined reference to `mpi_f08_interfaces_callbacks_'
test.f:(.data+0x74): u
Paul and Jeff,
I additionally installed PGI14.4 and check the behavior.
Then, I confirmed that both versions create same results.
PGI14.7:
[mishima@manage work]$ mpif90 test.f -o test.ex --showme
pgfortran test.f -o test.ex
-I/home/mishima/opt/mpi/openmpi-1.8.2rc2-pgi14.7/include
-I/home/mishim
On Jul 28, 2014, at 11:43 PM, tmish...@jcity.maeda.co.jp wrote:
> [mishima@manage work]$ mpif90 test.f -o test.ex
> /tmp/pgfortran65ZcUeoncoqT.o: In function `.C1_283':
> test.f:(.data+0x6c): undefined reference to `mpi_f08_interfaces_callbacks_'
> test.f:(.data+0x74): undefined reference to `mpi_
Tetsuya,
I found that the behavior of pgf90 changed somewhere between versions 13.6
and 14.1.
My previous reports were mostly based on my testing of 13.6.
So, I have probably been seeing an issue entirely different than yours.
I am testing 14.4 now and hope to be able to reproduce the problem you
Jeff,
I am not "screaming" for a return of support for the PGI compilers.
I will also note that "use mpi" works fine; only the F2008 support is
lacking.
Rather than complain I am offering to help test any solution that might be
offered.
I will also note that Nathan and Howard both have accounts a
On Jul 30, 2014, at 12:36 AM, Paul Hargrove wrote:
> Unfortunately, this (and https://svn.open-mpi.org/trac/ompi/changeset/31588
> that followed) represent a REGRESSION in that between 1.8.1 and 1.8.2rc2 Open
> MPI has lost support for F08 with the PGI compilers.
Yes, and the answer is for PGI
I will fix this tomorrow
Right now, --enable-mpi-fortran is --enable-mpi-fortran=yes is
--enable-mpi-fortran=all :
So configure aborts if not all bindings can be built
In ompi_configure_options.m4 :
OMPI_FORTRAN_USER_REQUESTED=0
108 case "x$enable_mpi_fortran" in
109 x)
110
Ummthis really broke things now. I can't build the fortran bindings at all,
and I don't have a PGI compiler. I also didn't specify a level of Fortran
support, but just had --enable-mpi-fortran
Maybe we need to revert this commit until we figure out a better solution?
On Jul 30, 2014, at 12:
Paul,
this is a fair point.
i commited r32354 in order to abort configure in this case
Cheers,
Gilles
On 2014/07/30 15:11, Paul Hargrove wrote:
> On a related topic:
>
> I configured with an explicit --enable-mpi-fortran=usempif08.
> Then configure found PROCEDURE was missing/broken.
> The res
Hi Paul, thank you for your comment.
I don't think my mpi_f08.mod is older one, because the time stamp is
equal to the time when I rebuilt them today.
[mishima@manage openmpi-1.8.2rc2-pgi14.7]$ ll lib/mpi*
-rwxr-xr-x 1 mishima mishima315 Jul 30 12:27 lib/mpi_ext.mod
-rwxr-xr-x 1 mishima mis
This is another one.
(See attached file: openmpi-1.8.2rc2-pgi14.7.tar.gz)
Tetusya
> Tetsuya --
>
> I am unable to test with the PGI compiler -- I don't have a license. I
was hoping that LANL would be able to test today, but I don't think they
got to it.
>
> Can you send more details?
>
> E.g.
Hi Jeff,
Sorry for poor information and late reply. Today, I attended a very very
long meeting ...
Anyway, I attached compile-output and configure-log.
(due to file size limitation, I send them in twice)
I hope you could find the problem.
(See attached file: openmpi-1.8-pgi14.7.tar.gz)
Regar
On a related topic:
I configured with an explicit --enable-mpi-fortran=usempif08.
Then configure found PROCEDURE was missing/broken.
The result is that the build continued, but without the requested f08
support.
If the user has explicitly enabled a given level of Fortran support, but it
cannot be
Paul,
i am sorry i missed that.
and you are right, 1.8.1 and 1.8 from svn differs :
from svn (config/ompi_setup_mpi_fortran.m4)
# Per https://svn.open-mpi.org/trac/ompi/ticket/4590, if the
# Fortran compiler doesn't support PROCEDURE in the way we
# want/need, disable the mpi_f08 mod
On Tue, Jul 29, 2014 at 9:09 PM, Gilles Gouaillardet <
gilles.gouaillar...@iferc.org> wrote:
> openpmi 1.8 (svn checkout) does not build the usempif08 bindings if
> PROCEDURE is not supported.
>
I have just verified that this requirement for PROCEDURE support is a
change in behavior between 1.8.
Giles,
If you look more carefully at the output I provided you will see that 1.8.1
*does* test for PROCEDURE support and finds it lacking. BOTH outputs
include:
checking if Fortran compiler supports PROCEDURE... no
However in the 1.8.1 case that is apparently not sufficient to disqualify
buildi
Paul,
from the logs, the only difference i see is about Fortran PROCEDURE.
openpmi 1.8 (svn checkout) does not build the usempif08 bindings if
PROCEDURE is not supported.
from the logs, openmpi 1.8.1 does not check whether PROCEDURE is
supported or not
here is the sample program to check PROCED
Sorry for poor information. I attached compile-output and configure-log.
I hope you could find the problem.
(See attached file: openmpi-pgi14.7.tar.gz)
Regards,
Tetsuya Mishima
> Tetsuya --
>
> I am unable to test with the PGI compiler -- I don't have a license. I
was hoping that LANL would b
On Tue, Jul 29, 2014 at 6:38 PM, Paul Hargrove wrote:
>
> On Tue, Jul 29, 2014 at 6:33 PM, Paul Hargrove wrote:
>
>> I am trying again with an explicit --enable-mpi-fortran=usempi at
>> configure time to see what happens.
>>
>
> Of course that should have said --enable-mpi-fortran=usempif08
>
I
On Tue, Jul 29, 2014 at 6:33 PM, Paul Hargrove wrote:
> I am trying again with an explicit --enable-mpi-fortran=usempi at
> configure time to see what happens.
>
Of course that should have said --enable-mpi-fortran=usempif08
--
Paul H. Hargrove phhargr...@lbl.gov
Futu
On Tue, Jul 29, 2014 at 4:23 PM, Jeff Squyres (jsquyres) wrote:
> Tetsuya --
>
> I am unable to test with the PGI compiler -- I don't have a license. I
> was hoping that LANL would be able to test today, but I don't think they
> got to it.
>
> Can you send more details?
>
> E.g., can you send th
If I read the original email correctly then 1.8.2rc2 also failed on
pgi-13.10.
At the moment I am just hoping to reproduce at all.
-Paul
On Tue, Jul 29, 2014 at 4:46 PM, Larry Baker wrote:
> PGI 14.7 is VERY new -- I just received the announcement on Sunday.
>
> Larry Baker
> US Geological Sur
PGI 14.7 is VERY new -- I just received the announcement on Sunday.
Larry Baker
US Geological Survey
650-329-5608
ba...@usgs.gov
On 29 Jul 2014, at 4:25 PM, Paul Hargrove wrote:
> I have license for PGI and installations of 14.1 and 14.4
> I will see what I can do today in terms of testing.
>
I have license for PGI and installations of 14.1 and 14.4
I will see what I can do today in terms of testing.
-Paul
On Tue, Jul 29, 2014 at 4:23 PM, Jeff Squyres (jsquyres) wrote:
> Tetsuya --
>
> I am unable to test with the PGI compiler -- I don't have a license. I
> was hoping that LANL wo
Tetsuya --
I am unable to test with the PGI compiler -- I don't have a license. I was
hoping that LANL would be able to test today, but I don't think they got to it.
Can you send more details?
E.g., can you send the all the stuff listed on
http://www.open-mpi.org/community/help/ for 1.8 and 1
Hi folks,
I tried to build openmpi-1.8.2rc2 with PGI-14.7 and execute a sample
program. Then, it causes linking error:
[mishima@manage work]$ cat test.f
program hello_world
use mpi_f08
implicit none
type(MPI_Comm) :: comm
integer :: myid, npes, ierror
integer
44 matches
Mail list logo