Phillip Johnston

I have no stance on these functions :). I haven't developed a system that has required them, and you are the first to ask. No technical or ideological reason.

[picolibc (newlib-nano) has full support](https://github.com/picolibc/picolibc/blob/main/doc/printf.md). I only mention as an immediate solution - I assume you are here because you do not wish to use newlib.

Looking over these functions, one blocker is that I do not actually support `FILE` or `stdin/out/err` in this library, so it would be gated on having a suitable solution for...

I'm happy to hear about any and all such instances. Part of my goal back-in-the-day when I started this library was cleaning up long-used libc code that was worrying.

We can test this out compilation-wise with clang ``` llc --version ... riscv32 - 32-bit RISC-V riscv64 - 64-bit RISC-V ... ```

Started this work, but errno not actually implemented.

__thread will likely not work because of the pthread dependency, and we'll want to get it working with an RTOS (as well as bare metal). We'll probably need to add...

Feel free to give it a shot if you want - it will probably be a while before I get around to a proper errno :) > On 3Aug2018, at...

printf test compilation errors reported via user: ``` Compiling C++ object printf_tests.p/subprojects_printf_test_test_suite.cpp.o FAILED: printf_tests.p/subprojects_printf_test_test_suite.cpp.o c++ -Iprintf_tests.p -I. -I.. -Isubprojects/printf/test -I../subprojects/printf/test -I../arch/aarch64/include -I../arch/aarch64/include/_types -fcolor-diagnostics -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++11 -O0 -g -MD...

Unused argument (I mean, I don't even enable this) ``` clang: warning: argument unused during compilation: '-fstack-clash-protection' ```