| Issue |
208579
|
| Summary |
Improving usability of modular printf
|
| Labels |
libc
|
| Assignees |
mysterymath
|
| Reporter |
Prabhuk
|
While trying to use the LLVM libc built with modular printf which brings in float parsing based on format strings used in the code, noticed a few challenges.
I had a case where the float parsing code was linked in correctly but it was linked in quietly and there is no way for the user to systematically catch when their code size increases due to this.
The second issue was due to wrapper functions around print family functions not carrying the correct function attributes on the client side which forces float parsing code to be linked in as we cannot reason about the format string at compile time. It is a challenge to debug and fix such cases.
I have not thought about how exactly the user can be helped to handle these cases but it will be helpful to have warnings/diagnostics user can opt into while using modular printf so they can identify unexpected "modules" (float parsing in this case) getting linked in. Additional user guide on how the users should handle wrapper functions and any other relevant details to get started will be useful as well.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
