This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [build] Move libgcov support to toplevel libgcc
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>, gcc-patches at gcc dot gnu dot org, Paolo Bonzini <bonzini at gnu dot org>, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, Ian Lance Taylor <iant at google dot com>
- Date: Fri, 8 Jul 2011 20:55:35 +0200
- Subject: Re: [build] Move libgcov support to toplevel libgcc
- References: <yddsjqhypn5.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <Pine.LNX.4.64.1107081424140.22395@digraph.polyomino.org.uk>
> On Fri, 8 Jul 2011, Rainer Orth wrote:
>
> > And another easy one: moving libgcov over to libgcc.
>
> Do you have any specific plans regarding gcov-io.c and gcov-io.h? Because
> they are genuinely used on both the host and the target they are a
> trickier case; I wonder if they should end up in their own toplevel
> directory like libdecnumber, building a proper library that exports
> different functions when configured for the host than for the target, that
> for the target gets included in libgcov and that for the host gets linked
> into cc1, gcov and gcov-dump rather than having files do the present
> '#include "gcov-io.c"'.
I would also preffer libgcov to go into its own toplevel directory,
especially because there are plans to add non-stdlib i/o into it i.e.
for kernel profiling. that way it would be handy to have libgcov
as a toplevel library with its own configure that allows it to be build
independently of rest of GCC.
Honza
>
> --
> Joseph S. Myers
> joseph@codesourcery.com