PGI no longer suprises me with how bad it is. The lines in question look ok to me. We can fix this (and remove the common symbols) by removing the initializers and making the variables static. I will go ahead and do this.
-Nathan
On Wed, Jul 01, 2015 at 05:41:59AM -0700, Paul Hargrove wrote:
> I find that PGI version 9, 10, 11, 12, 13 and 14 all fail "make check"
> with last night's master tarball. All expect 9 fail with pretty much the
> same message:
> CC opal_condition.o
> PGC-S-0155-Empty initializer not supported
>
> (/scratch/scratchdirs/hargrove/OMPI/openmpi-master-linux-x86_64-pgi-14.7/openmpi-dev-2014-gc8730b5/test/threads/opal_condition.c:
> 48)
> PGC-S-0155-Empty initializer not supported
>
> (/scratch/scratchdirs/hargrove/OMPI/openmpi-master-linux-x86_64-pgi-14.7/openmpi-dev-2014-gc8730b5/test/threads/opal_condition.c:
> 49)
> PGC-S-0155-Empty initializer not supported
>
> (/scratch/scratchdirs/hargrove/OMPI/openmpi-master-linux-x86_64-pgi-14.7/openmpi-dev-2014-gc8730b5/test/threads/opal_condition.c:
> 50)
> PGC/x86-64 Linux 14.7-0: compilation completed with severe errors
> make[3]: *** [opal_condition.o] Error 2
> Those lines are:
> opal_mutex_t mutex = {};
> opal_condition_t thr1_cond = {};
> opal_condition_t thr2_cond = {};
> I have no clue why pgi won't accept that when every other compiler does.
> Tests were on NERSC's Hopper and Carver, where Howard should be able to
> reproduce.
> -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/07/17580.php
pgpFxPFlAdDNF.pgp
Description: PGP signature
