Re: [devel] uint32_t typedef differences causes issues


Kumar Gala <kumar.gala@...>
 

So I was looking at moving minimal libc’s typedef of {u}int32_t to match newlib. It looks all platforms except elfiamcu define:

#define __INT32_TYPE__ long int
#define __UINT32_TYPE__ long unsigned int

Where elfiamcu defines:

#define __INT32_TYPE__ int
#define __UINT32_TYPE__ unsigned int

So now I’m at a loss of how we unify things across all our arch’s and toolchains. This seems to lead us down the use of PRI.32 macros.

Thoughts?

- k

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