printk: Add tests for print format

[yperess]

Add tests to verify that the various PRI\w\d+ macros map to the
correct U?INT\d+_C macros.

Signed-off-by: Yuval Peress [email protected]

Fixes #44199

[yperess]

This is a PR that's building on @MaureenHelm 's find at #41735 (review). It's still a work in progress, but basically I'm finding that in the Kinetis K6X a value such as 8U is an unsigned long instead of the expected unsigned int. I'm still not sure what the right fix is.

[stephanosio]

the changes to zephyr_stdint.h should be a separate commit (you can cherry-pick the existing commit 2f6c982).

By the way, during local testing, I saw a bunch of timeouts from twister even though the actual QEMU output was correct.

[stephanosio]

toolchain: Add missing U?INT(32|64)_C implementations

These implementations were missing/incorrect for several architectures
that need the zephyr_stdint.h.

Signed-off-by: Yuval Peress <[email protected]>

As noted in #44199 and 2f6c982, these macros were not missing -- they are always internally defined by the toolchain/compiler.

The problem is that Zephyr defines its own stdint types and, unless we re-define/override these integer constant macros as well, they are not going to correspond.

Please update the commit message accordingly.

[yperess]

toolchain: Add missing U?INT(32|64)_C implementations

These implementations were missing/incorrect for several architectures
that need the zephyr_stdint.h.

Signed-off-by: Yuval Peress <[email protected]>

As noted in #44199 and 2f6c982, these macros were not missing -- they are always internally defined by the toolchain/compiler.

The problem is that Zephyr defines its own stdint types and, unless we re-define/override these integer constant macros as well, they are not going to correspond.

Please update the commit message accordingly.

Sorry, finally figured out how to cherry pick from the other repo without adding another remote to my git :) I'm still seeing the timeouts so I'll figure that out and remove the WIP label then

[stephanosio]

@yperess By the way, what was causing the timeout earlier?

[yperess]

@yperess By the way, what was causing the timeout earlier?

A copy paste error in the expected console output. I didn't change the numbers to octal base for PRIo* ☺️