This is the mail archive of the
mailing list for the GCC project.
Re: Unexpected presence of __eprintf in libgcc.a when using newlib
- From: Andrew Pinski <pinskia at gmail dot com>
- To: "Thomas Preud'homme" <thomas dot preudhomme at arm dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>
- Date: Tue, 8 Apr 2014 20:19:46 -0700
- Subject: Re: Unexpected presence of __eprintf in libgcc.a when using newlib
- Authentication-results: sourceware.org; auth=none
- References: <005201cf5306$7de51cb0$79af5610$ at arm dot com> <CAKOQZ8xSmAPN1b2QXn9OjPnf_j6BLXWhFQnSKhsRTu3VCMo67w at mail dot gmail dot com> <005901cf53a1$db5fea50$921fbef0$ at arm dot com>
On Tue, Apr 8, 2014 at 8:14 PM, Thomas Preud'homme
>> From: Ian Lance Taylor [mailto:email@example.com]
>> I don't think anything uses __eprintf any more. The function has been
>> left behind for very very very old systems. Actually we could
>> probably remove it now. Probably the old support for not building
>> __eprintf when --with-newlib was specified has bitrotted.
> Removing it would be great. I'm working on a patch to automatically pull support
> for floating point in printf/scanf and having eprintf in libgcc lead to such support
> to be always pulled in since it calls printf and the format used is not a string litteral.
I think your patch is broken since the object file (_eprintf.o) should
not be pulled in unless it is used and it is part of an archive and
for archives cause the linker to only bring in object files which have
things referenced to them.
> Should I propose a patch to remove it?
> Best regards,