I don't have any problem with changing minimal libc to have the same definitions as newlib. I can't say one way or another whether we will end up supporting 16-bit targets but I think we should do

There is a difference between strictly being compliant and doing what makes things easier for the users. I would gather that most users would expect a uint32_t to be printable with %d, and we have a

I’d start with a basic board port and get serial going. From there we can see what makes sense w/regards to I2C & SPI drivers. - k

Hi Kumar, Waiting for your response !! Thanks, Abhinav

How easily can we feed different -W options to the /ext part of the tree, or is that painful ? Cheers /Marcus

I turned on -Wformat, and fixed a great deal of malfeasance across the codebase. I would be strongly opposed to disabling this warning. It's a warning. The code still compiles for end users. We only

I don't think there's anything wrong with newlib. The only requirement on the C library is that uint32_t is 32-bits wide (i.e. no padding) and the newlib implementation meets this

Moving this to the devel@ mailing list. The relevant jira: https://jira.zephyrproject.org/browse/ZEP-948 Anas

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

If i recall correctly -Wformat also affects scanf() checks. It would be bad to leave these calls unchecked. -- Maciek Borzecki

I think it'd be better to fix things like this. Although it sometimes has problems, -Wformat also catches a lot of things that are indeed wrong. It isn't always going to be possible to make it

We could also always turn off -Wformat. - k

NEW JIRA items within last 24 hours: 2 [ZEP-1599] printk() support for the '-' indicator in format string (left justifier) https://jira.zephyrproject.org/browse/ZEP-1599 [ZEP-1600] Quark Se

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/10273 : Bluetooth: L2CAP: Only set state for dynamic channels - https://gerrit.zephyrproject.org/r/10272 : Merge net branch into

Paul, Thank you for the update. Maybe it makes sense to move this to the source tree and have it as part of the documentation alongside the samples. This way the information for older versions will

Hello, This is just a background notice that the page https://wiki.zephyrproject.org/view/Networking-with-Qemu , which previously contained information for 1.6 and earlier, was updated for the master

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

Thank you, Joseph.

Hi, A bit off topic, but could someone shed some light on why Zephyr has support for two libc implementations? ie Why not just always use newlib ? -- BR Szymon Janc

marcus.shawcroft(a)gmail.com> wrote: That sounds reasonable to me. Change minimal libc to align with newlib and apply 2, the question is if we want to enforce usage of PRI macros. Anas