> [...] >>> We could switch to "wrap" to align with clang, but in that case it would >>> be up to the user to provide a "host" stdint.h that contains sensible >>> definitions for BPF. The kernel selftests, for example, would need to >>> do so to avoid including /usr/include/stdint.h that more likely than not >>> will provide incorrect definitions for int64_t and friends... >> >> Would it be possible to push a branch that uses '=wrap' thing >> somewhere? So that it could be further tested to see if there are >> more issues with selftests. > > No need. After reflecting a bit I can't see why the requirements on the > "host" stdint.h must be different for BPF than for any other target: its > contents must match the expectations of the compiler for the arch. If > it doesn't... well, it is not the responsibility of the compiler to > assure that. I will install a patch to switch to the wrapper stdint.h. https://gcc.gnu.org/pipermail/gcc-patches/2025-January/672508.html
