Hi Rainer,
On 1/18/24 10:34, Rainer Orth wrote:
Hi Arthur,
Yes, I was talking about this on IRC the other day - if we do run in a
situation where we have more than UINT32_MAX procedural macros in memory
we have big issues. These debug prints will probably end up getting removed
soon as they clutter the output a lot for little information.
makes sense, especially if they break the build once in a while ;-)
I don't mind doing it the right way for our regular prints, but we have not
been using PRIu64 in our codebase so far, so I'd rather change all those
incriminating format specifiers at once later down the line - this patch
was pushed so that 32bit targets could bootstrap the Rust frontend for now.
Makes sense: using different styles throughout the codebase only creates
confusion.
On a related issue: didn't you have some 32-bit host in your CI? I
remember having similar issues in the past which could easily be avoided
in advance this way.
We do have 32 bits runners in the buildbot Mark takes care of, but they
were not running bootstrap builds so this was getting ignored as it only
produced a warning. Definitely something I want to fix quickly.
Thanks.
Rainer
