Keith Packard
Keith Packard
Makes sense. I think you could pretty easily build an implementation of the vasnprintf API using vsnprintf and vasprintf which did exactly that at modest cost in code space. It...
No known issues for picolibc for 3.7.0 -- current release is the same as zephyr uses.
Looks like my duplicate name checking code is busted -- it's finding some duplicate *file* names, not duplicate *function* names and complaining about that. This patch might help? ``` diff...
The patch I showed is already upstream, and I'll be releasing that shortly. Thanks for testing!
That looks like it's trying to build the picolibc C++ header test. Maybe that just doesn't work in this environment? Are you expecting the toolchain to have C++ support?
If you split out the printf from scanf selection, at least you'd avoid pulling in the scanf code with this?
Looks like scripts/duplicate-names needs a fix to ignore 'N' symbols (the nm manual says those are debugging symbols). The build is just trying to make sure each C library symbol...
Check out https://github.com/picolibc/picolibc/pull/890 -- that has your change to fix this.
oh, picolibc is also happy to use llvm's ABI support library that replaces libgcc. I've got several CI tests which don't use any gcc bits.
> Do you mean LLVM's "compiler-rt" library (https://github.com/llvm/llvm-project/tree/main/compiler-rt)? Yeah, that's the one -- I'd forgotten the name.