Xtensa format specifier

[cmt0]

Differential Revision: D87159004

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15842

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit e335d5e with merge base b1e3e28 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@cmt0 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D87159004.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[Copilot]

Pull Request Overview

This PR updates the printf format specifiers for size_t and ssize_t types on the Xtensa platform, changing from "lu"/"ld" (long unsigned/long int) to "u"/"d" (unsigned int/int) format specifiers.

• Changed ET_PRIsize_t from "lu" to "u" for Xtensa
• Changed ET_PRIssize_t from "ld" to "d" for Xtensa

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Using 'u' and 'd' format specifiers assumes size_t/ssize_t are the same size as unsigned int/int on Xtensa. If size_t is larger than unsigned int (e.g., on a 64-bit pointer model with 32-bit int), this will cause truncation and incorrect output. The comment mentions 'zu' is not supported, but typically platforms support either 'zu' or provide alternative size-matching specifiers. Consider verifying that size_t is definitively the same size as unsigned int on Xtensa, or use a cast to unsigned int/int at call sites with appropriate range checking.

[lucylq]

@cmt0 this seems like a valid comment - are size_t/ssize_t the same as unsigned int/int on Xtensa 32-bit/64-bit?