Hmmm...I hate chasing compiler bugs, and since this is only a warning, I would
tend to defer making changes and just let folks push on PGI to fix their bug.
Anyone object to that strategy?
On Jan 17, 2014, at 12:04 PM, Paul Hargrove wrote:
> Larry,
>
> So, if I follow
Larry,
So, if I follow your report correctly is is probably the "static" (not the
"const") property of the string literals' type that leads pgcc to warn. If
that is the case, then I agree that this is NOT a warning that is
consistent with the C standard's rules for type compatibility. Thus I
Paul,
From what I can see in the arguments to OPAL_OUTPUT_VERBOSE() in line 356 at
https://bitbucket.org/ompiteam/ompi-svn-mirror/src/f48eeda443104a64dc89e4f5fab4c940e44d8615/opal/mca/db/hash/db_hash.c,
this is the same PGI bug I reported 22 Jul 2010, which was assigned TPR 17139.
> Customer
Paul, Ralph,I had several issues in 2010 with with PGI pgcc being overly picky about type mismatches. Attached are my e-mails from that time. I was working on NetCDF and OpenMPI. In the OpenMPI report (17 Aug 2010), I found problems in conditional expressions. The last e-mail in the thread
My builds of the trunk with pgcc-13.10 turned up the following warnings:
PGC-W-0095-Type cast required for this conversion
(/scratch/scratchdirs/hargrove/OMPI/openmpi-trunk-linux-x86_64-pgi-13.10/openmpi-1.9a1r30302/opal/mca/db/hash/db_hash.c:
354)
PGC-W-0095-Type cast required for this