Re: [OMPI devel] [v2.x] printf format warnings w/ -m32

If there is a size_t vs PRIsize_t mismatch then it is probably a result of less-than-perfect integration in the Clang private headers (stddef.h in particular). I will make a point not to trust Clang for this class of warning in the future. What about the sharedfp warnings such as the following:

Re: [OMPI devel] [v2.x] printf format warnings w/ -m32

I took a look at this, and the problem isn’t in the print statements. The problem is that PRIsize_t is being incorrectly set to “unsigned long” instead of something correct for the -m32 directive in that environment > On May 6, 2016, at 9:48 AM, Paul Hargrove wrote: > >

[OMPI devel] [v2.x] printf format warnings w/ -m32

The 96 printf format warnings in the attachment come from an Linux/x86-64 system w/ Clang and "-m32". Some of the warnings are "size_t" vs "unigned long", which is harmless since both are 32-bits. However, there are several cases in sharedfp/sm where a 64-bit (long long) format has a 32-bit