(the fix has been merged in to v1.8 and v1.10 branches)
> On Aug 20, 2015, at 12:18 PM, Nathan Hjelm <hje...@lanl.gov> wrote:
>
>
> I see the problem. Both Ralph and I missed an error in the
> cherry-pick. For add_32 in the ia32 atomics we were checking for
> OPAL_GCC_INLINE_ASSEMBLY instead of OMPI_GCC_INLINE_ASSEMBLY.
>
> -Nathan
>
> On Thu, Aug 20, 2015 at 03:01:35PM +0000, Jeff Squyres (jsquyres) wrote:
>> Paul --
>>
>> I see that there was an ASM change in 1.8.8. At first look, it seems
>> harmless / shouldn't have caused this kind of problem.
>>
>> Nathan is checking into it...
>>
>>
>>
>>> On Aug 14, 2015, at 9:52 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>>>
>>> I have a systems running Solaris 11.1 on x86-64 hardware and 11.2 in an
>>> x86-64 VM.
>>> To the extent I have tested the results are the same on both, despite
>>> gcc-4.5.2 vs 4.8.2
>>>
>>> I have normally tested only the Sun/Oracle Studio compilers on these
>>> systems.
>>> However, today I gave the vendor-provided gcc, g++ and gfortran in /usr/bin
>>> a try.
>>> So I configured the OpenMPI 1.10.0rc3 tarball with NO arguments to
>>> configure.
>>>
>>> When doing so I see tons of warnings like:
>>>
>>> ../../../../openmpi-1.10.0rc3/opal/include/opal/sys/atomic.h:393:9:
>>> warning: `opal_atomic_add_32' used but never defined
>>> ../../../../openmpi-1.10.0rc3/opal/include/opal/sys/atomic.h:401:9:
>>> warning: `opal_atomic_sub_32' used but never defined
>>>
>>> and an eventual link failure to match:
>>>
>>> CCLD libopen-pal.la
>>> Text relocation remains referenced
>>> against symbol offset in file
>>> opal_atomic_add_32 0x1e4
>>> runtime/.libs/opal_progress.o
>>> opal_atomic_sub_32 0x234
>>> runtime/.libs/opal_progress.o
>>> ld: fatal: relocations remain against allocatable but non-writable sections
>>> collect2: ld returned 1 exit status
>>>
>>>
>>>
>>> Here is the possibly-relevant portion of the configure output:
>>>
>>> checking if gcc -std=gnu99 supports GCC inline assembly... yes
>>> checking if gcc -std=gnu99 supports DEC inline assembly... no
>>> checking if gcc -std=gnu99 supports XLC inline assembly... no
>>> checking for assembly format... default-.text-.globl-:--.L-@-1-0-1-1-0
>>> checking for assembly architecture... IA32
>>> checking for builtin atomics... BUILTIN_NO
>>> checking for perl... perl
>>> checking for pre-built assembly file... yes (atomic-ia32-linux-nongas.s)
>>> checking for atomic assembly filename... atomic-ia32-linux-nongas.s
>>>
>>>
>>> The same problem is present in Open MPI 1.8.8, but 1.8.7 builds just fine.
>>>
>>> Note that on Solaris the default ABI is ILP32 (e.g. default to -m32 rather
>>> than -m64).
>>> There are no problems with LP64 builds ("-m64" in *FLAGS and the wrapper
>>> flags).
>>> There are also no problems with either ILP32 or LP64 and the Studio
>>> compilers.
>>> Only gcc with (default) 32-bit target experiences this failure.
>>>
>>> -Paul
>>>
>>> --
>>> Paul H. Hargrove phhargr...@lbl.gov
>>> Computer Languages & Systems Software (CLaSS) Group
>>> Computer Science Department Tel: +1-510-495-2352
>>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>>> _______________________________________________
>>> devel mailing list
>>> de...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>> Link to this post:
>>> http://www.open-mpi.org/community/lists/devel/2015/08/17750.php
>>
>>
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> _______________________________________________
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2015/08/17766.php
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2015/08/17767.php
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
