Thanks for reporting this! Glad the problem is fixed. We will get this into 
2.0.2.

-Nathan

> On Sep 7, 2016, at 9:39 AM, Vallee, Geoffroy R. <valle...@ornl.gov> wrote:
> 
> I just tried the fix and i can confirm that it fixes the problem. :)
> 
> Thanks!!!
> 
>> On Sep 2, 2016, at 6:18 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
>> wrote:
>> 
>> Issue filed at https://github.com/open-mpi/ompi/issues/2044.
>> 
>> I asked Nathan and Sylvain to have a look.
>> 
>> 
>>> On Sep 1, 2016, at 9:20 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>>> 
>>> I failed to get PGI 16.x working at all (licence issue, I think).
>>> So, I can neither confirm nor refute Geoffroy's reported problems.
>>> 
>>> -Paul
>>> 
>>> On Thu, Sep 1, 2016 at 6:15 PM, Vallee, Geoffroy R. <valle...@ornl.gov> 
>>> wrote:
>>> Interesting, I am having the problem with both 16.5 and 16.7.
>>> 
>>> My 2 cents,
>>> 
>>>> On Sep 1, 2016, at 8:25 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>>>> 
>>>> FWIW I have not seen problems when testing the 2.0.1rc2 w/ PGI versions 
>>>> 12.10, 13.9, 14.3 or 15.9.
>>>> 
>>>> I am going to test 2.0.2.rc3 ASAP and try to get PGI 16.4 coverage added in
>>>> 
>>>> -Paul
>>>> 
>>>> On Thu, Sep 1, 2016 at 12:48 PM, Jeff Squyres (jsquyres) 
>>>> <jsquy...@cisco.com> wrote:
>>>> Please send all the information on the build support page and open an 
>>>> issue at github.  Thanks.
>>>> 
>>>> 
>>>>> On Sep 1, 2016, at 3:41 PM, Vallee, Geoffroy R. <valle...@ornl.gov> wrote:
>>>>> 
>>>>> This is indeed a little better but still creating a problem:
>>>>> 
>>>>> CCLD     opal_wrapper
>>>>> ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
>>>>> `_opal_progress_unregister':
>>>>> /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:459:
>>>>>  undefined reference to `opal_atomic_swap_64'
>>>>> ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
>>>>> `_opal_progress_register':
>>>>> /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:398:
>>>>>  undefined reference to `opal_atomic_swap_64'
>>>>> make[2]: *** [opal_wrapper] Error 2
>>>>> make[2]: Leaving directory 
>>>>> `/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/tools/wrappers'
>>>>> make[1]: *** [all-recursive] Error 1
>>>>> make[1]: Leaving directory 
>>>>> `/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal'
>>>>> make: *** [all-recursive] Error 1
>>>>> 
>>>>> $ nm libopen-pal.a  | grep atomic
>>>>>               U opal_atomic_cmpset_64
>>>>> 0000000000000ab0 t opal_atomic_cmpset_ptr
>>>>>               U opal_atomic_wmb
>>>>> 0000000000000950 t opal_lifo_push_atomic
>>>>>               U opal_atomic_cmpset_acq_32
>>>>> 00000000000003d0 t opal_atomic_lock
>>>>> 0000000000000450 t opal_atomic_unlock
>>>>>               U opal_atomic_wmb
>>>>>               U opal_atomic_ll_64
>>>>>               U opal_atomic_sc_64
>>>>>               U opal_atomic_wmb
>>>>> 0000000000001010 t opal_lifo_pop_atomic
>>>>>               U opal_atomic_cmpset_acq_32
>>>>> 00000000000004b0 t opal_atomic_init
>>>>> 00000000000004e0 t opal_atomic_lock
>>>>>               U opal_atomic_mb
>>>>> 0000000000000560 t opal_atomic_unlock
>>>>>               U opal_atomic_wmb
>>>>>               U opal_atomic_add_32
>>>>>               U opal_atomic_cmpset_acq_32
>>>>> 0000000000000820 t opal_atomic_init
>>>>> 0000000000000850 t opal_atomic_lock
>>>>>               U opal_atomic_sub_32
>>>>>               U opal_atomic_swap_64
>>>>> 00000000000008d0 t opal_atomic_unlock
>>>>>               U opal_atomic_wmb
>>>>> 0000000000000130 t opal_atomic_init
>>>>> atomic-asm.o:
>>>>> 0000000000000138 T opal_atomic_add_32
>>>>> 0000000000000018 T opal_atomic_cmpset_32
>>>>> 00000000000000c4 T opal_atomic_cmpset_64
>>>>> 000000000000003c T opal_atomic_cmpset_acq_32
>>>>> 00000000000000e8 T opal_atomic_cmpset_acq_64
>>>>> 0000000000000070 T opal_atomic_cmpset_rel_32
>>>>> 0000000000000110 T opal_atomic_cmpset_rel_64
>>>>> 0000000000000000 T opal_atomic_mb
>>>>> 0000000000000008 T opal_atomic_rmb
>>>>> 0000000000000150 T opal_atomic_sub_32
>>>>> 0000000000000010 T opal_atomic_wmb
>>>>> 0000000000002280 t mca_base_pvar_is_atomic
>>>>>               U opal_atomic_ll_64
>>>>>               U opal_atomic_sc_64
>>>>>               U opal_atomic_wmb
>>>>> 0000000000000900 t opal_lifo_pop_atomic
>>>>> 
>>>>>> On Sep 1, 2016, at 3:16 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
>>>>>> wrote:
>>>>>> 
>>>>>> Can you try the latest v2.0.1 nightly snapshot tarball?
>>>>>> 
>>>>>> 
>>>>>>> On Sep 1, 2016, at 2:56 PM, Vallee, Geoffroy R. <valle...@ornl.gov> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>> Hello,
>>>>>>> 
>>>>>>> I get the following problem when we compile OpenMPI-2.0.0 (it seems to 
>>>>>>> be specific to 2.x; the problem did not appear with 1.10.x) with PGI:
>>>>>>> 
>>>>>>> CCLD     opal_wrapper
>>>>>>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>>>>>>> `opal_atomic_sc_64'
>>>>>>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>>>>>>> `opal_atomic_ll_64'
>>>>>>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>>>>>>> `opal_atomic_swap_64'
>>>>>>> make[1]: *** [opal_wrapper] Error 2
>>>>>>> 
>>>>>>> It is a little for me to pin point the exact problem but i can see the 
>>>>>>> following:
>>>>>>> 
>>>>>>> $ nm ./.libs/libopen-pal.so | grep atomic
>>>>>>> 0000000000026320 t 00000017.plt_call.opal_atomic_add_32
>>>>>>> 0000000000026250 t 00000017.plt_call.opal_atomic_cmpset_32
>>>>>>> 0000000000026780 t 00000017.plt_call.opal_atomic_cmpset_64
>>>>>>> 00000000000280c0 t 00000017.plt_call.opal_atomic_cmpset_acq_32
>>>>>>> 0000000000028ae0 t 00000017.plt_call.opal_atomic_ll_64
>>>>>>> 0000000000027fe0 t 00000017.plt_call.opal_atomic_mb
>>>>>>> 0000000000027d50 t 00000017.plt_call.opal_atomic_rmb
>>>>>>> 0000000000028500 t 00000017.plt_call.opal_atomic_sc_64
>>>>>>> 0000000000027670 t 00000017.plt_call.opal_atomic_sub_32
>>>>>>> 0000000000026da0 t 00000017.plt_call.opal_atomic_swap_64
>>>>>>> 0000000000027050 t 00000017.plt_call.opal_atomic_wmb
>>>>>>> 000000000005e6a0 t mca_base_pvar_is_atomic
>>>>>>> 000000000004715c T opal_atomic_add_32
>>>>>>> 000000000004703c T opal_atomic_cmpset_32
>>>>>>> 00000000000470e8 T opal_atomic_cmpset_64
>>>>>>> 0000000000047060 T opal_atomic_cmpset_acq_32
>>>>>>> 000000000004710c T opal_atomic_cmpset_acq_64
>>>>>>> 000000000002a610 t opal_atomic_cmpset_ptr
>>>>>>> 0000000000047094 T opal_atomic_cmpset_rel_32
>>>>>>> 0000000000047134 T opal_atomic_cmpset_rel_64
>>>>>>> 0000000000032cc0 t opal_atomic_init
>>>>>>> 0000000000033980 t opal_atomic_init
>>>>>>> 00000000000396a0 t opal_atomic_init
>>>>>>>             U opal_atomic_ll_64
>>>>>>> 000000000002e460 t opal_atomic_lock
>>>>>>> 0000000000032cf0 t opal_atomic_lock
>>>>>>> 00000000000339b0 t opal_atomic_lock
>>>>>>> 0000000000047024 T opal_atomic_mb
>>>>>>> 000000000004702c T opal_atomic_rmb
>>>>>>>             U opal_atomic_sc_64
>>>>>>> 0000000000047174 T opal_atomic_sub_32
>>>>>>>             U opal_atomic_swap_64
>>>>>>> 000000000002e4e0 t opal_atomic_unlock
>>>>>>> 0000000000032d70 t opal_atomic_unlock
>>>>>>> 0000000000033a30 t opal_atomic_unlock
>>>>>>> 0000000000047034 T opal_atomic_wmb
>>>>>>> 00000000000324d0 t opal_lifo_pop_atomic
>>>>>>> 00000000000cc260 t opal_lifo_pop_atomic
>>>>>>> 000000000002a490 t opal_lifo_push_atomic
>>>>>>> 
>>>>>>> Any idea of how to fix the problem?
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> _______________________________________________
>>>>>>> devel mailing list
>>>>>>> devel@lists.open-mpi.org
>>>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Jeff Squyres
>>>>>> jsquy...@cisco.com
>>>>>> For corporate legal information go to: 
>>>>>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>>>>> 
>>>>>> _______________________________________________
>>>>>> devel mailing list
>>>>>> devel@lists.open-mpi.org
>>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> devel mailing list
>>>>> devel@lists.open-mpi.org
>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>> 
>>>> 
>>>> --
>>>> Jeff Squyres
>>>> jsquy...@cisco.com
>>>> For corporate legal information go to: 
>>>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>>> 
>>>> _______________________________________________
>>>> devel mailing list
>>>> devel@lists.open-mpi.org
>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 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
>>>> devel@lists.open-mpi.org
>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>> 
>>> _______________________________________________
>>> devel mailing list
>>> devel@lists.open-mpi.org
>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>> 
>>> 
>>> 
>>> -- 
>>> 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
>>> devel@lists.open-mpi.org
>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>> 
>> 
>> -- 
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to: 
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>> 
>> _______________________________________________
>> devel mailing list
>> devel@lists.open-mpi.org
>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>> 
> 
> _______________________________________________
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

_______________________________________________
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Reply via email to