Consider rebasing your printf fork of mpaland/printf on eyalroz/printf #2694
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk#2694
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello RaspberryPI pico-SDK people,
It's been pointed out to me that your SDK's standalone print implementation is a copy, or fork, of Marco Paland standalone printf library code.
Well, as you may be aware, Mr. Paland had abandoned his repository over 5 years ago; but - development work has continued, in my own eyalroz/printf: A lot of bugs have had fixes integrated from other forks, or just fixed, period; output correctness has been improved (mpaland's code was failing in all sorts of combinations of flags and format specs) as well as features added - almost completing the C99 feature set.
I therefore suggest you consider rebasing your code onto the eyalroz/printf implementation.
I should perhaps mention that the embeddedartistry Arduino SDK has rebased from mpaland/printf to eyalroz/printf.
Might help with merging the Pico-SDK changes with changes in another repo: I've done some Git-fu to pull the Pico-SDK changes back out onto Marco's commit history: https://github.com/LukeShu/pico-fmt/tree/pico-sdk
Awesome, thanks - we'll look at updating this is the next minor release; though we do need to be wary of growing the printf library unconditionally (if the new code is bigger) since a lot of existing things may use printf and be tight on space.
@kilograham : About code size...
-Os, the result is pretty small.That said - I did not engage in minute optimizations for minimizing size, so I suppose it is up to you to consider the resulting size. I hope this works out :-)
Ah, sweet! The float internal representation option might be super cool too - since the old version always pulled in double