On Tue, Nov 03, 2020 at 01:12:29AM +0000, Joseph Myers wrote: > On Mon, 2 Nov 2020, Segher Boessenkool wrote: > > > > Also note that if you want to use printf as opposed to strfromf128 for > > > IEEE binary128 you'll need to use __printfieee128 (the version that > > > expects long double to be IEEE binary128) which was introduced in glibc > > > 2.32, so that doesn't help with the glibc version dependencies. > > > > libiberty has printf functions of its own, I was wondering if those work > > fine; if they do, that would solve all problems here. > > I don't see any meaningful kind of printf implementation in libiberty. > There are implementations of various printf functions in terms of other > printf functions (including vprintf in terms of vfprintf in terms of > _doprnt in terms of fprintf), but nothing that actually does the main work > of converting a floating-point value to a string without calling out to > some libc printf function.
I missed that "in terms of fprintf" step :-( Well, rats. Thanks for telling me about my stupidity! :-) Segher
