From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gcc-patches@gcc.gnu.org, Paolo Bonzini <bonzini@gnu.org>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Ian Lance Taylor <iant@google.com>
Subject: Re: [build] Move libgcov support to toplevel libgcc
Date: Fri, 08 Jul 2011 14:35:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1107081424140.22395@digraph.polyomino.org.uk> (raw)
In-Reply-To: <yddsjqhypn5.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
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"'.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-07-08 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 11:33 Rainer Orth
2011-07-08 11:42 ` Paolo Bonzini
2011-07-08 14:35 ` Joseph S. Myers [this message]
2011-07-08 15:43 ` Rainer Orth
2011-07-08 19:08 ` Jan Hubicka
2011-07-13 14:03 ` Rainer Orth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1107081424140.22395@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).