This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Unexpected presence of __eprintf in libgcc.a when using newlib
- From: Ian Lance Taylor <iant at google 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 07:35:03 -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>
On Tue, Apr 8, 2014 at 1:42 AM, Thomas Preud'homme
<thomas.preudhomme@arm.com> wrote:
>
> When playing with a toolchain built with --with-newlib switch, I recently noticed that libgcc.a includes __eprintf among its objects. However, gcc/doc/install.texi states that --with-newlib switches "causes @code{__eprintf} to be omitted from @file{libgcc.a} on the assumption that it will be provided by @samp{newlib}. And indeed, newlib provides __eprintf. Was the logic to omit __eprintf when newlib is used removed at some point for some reason or is it a bug?
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.
Ian