On Jan 17, 2014, at 12:44 PM, Paul Hargrove wrote:
> Ralph,
>
> I might be the most active lurker on Earth, but I am still that: an
> individual outside the OMPI core developers who follows the devel list. So,
> excepting bugs that cause me actual harm (and this is NOT one) I am usually
> h
Ralph,
I might be the most active lurker on Earth, but I am still that: an
individual outside the OMPI core developers who follows the devel list.
So, excepting bugs that cause me actual harm (and this is NOT one) I am
usually happy to defer to the core developers.
As I just sent in response to
Paul,
> 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.
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 your report correctly i
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
agr
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 i
Ralph,
You are probably right that the string literals are a likely cause (type
char[] ? ).
I will poke at this a bit by adding (char *) casts to see which argument(s)
are actually the cause and get back to you.
-Paul
On Fri, Jan 17, 2014 at 8:56 AM, Ralph Castain wrote:
> Hi Paul
>
> Looking
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 from
Hi Paul
Looking at these, I'm a tad puzzled. It would appear that PGI is complaining
about the fixed string being passed in the last three cases as there is no
(const char*)foo being used in those areas. Yet we use that same logic
elsewhere and your report isn't showing those as warnings.
Do y
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 conversion
10 matches
Mail list logo
