Re: uint32_t typedef differences causes issues


Anas Nashif
 

On Fri, Jan 20, 2017 at 11:12 AM, Kumar Gala <kumar.gala(a)linaro.org> wrote:


On Jan 20, 2017, at 7:37 AM, Patrik Flykt <Patrik.Flykt(a)linux.intel.com>
wrote:

On Fri, 2017-01-20 at 06:21 -0500, Anas Nashif wrote:
the question is if we want to enforce usage of PRI macros.
The de facto standard is unfortunately that %d and %u print integers up
to and including an uint32_t. Enforcing these to be expressed as PRIu32
in Zephyr will be less portable for external and internal developers.

From the error printout, my first conclusion is that there is a bug in
newlib, not the other way around.


Cheers,

Patrik
We could also always turn off -Wformat.
Any secure coding guideline will tell you to enable this in addition to
other options (-Wformat -Wformat-security -Werror=format-security), we are
working on such a guideline right now, so my assumption it will be there as
well.

Anas



- k

Join devel@lists.zephyrproject.org to automatically receive all group messages.