From: Paolo Bonzini <bonzini@gnu.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gcc-patches@gcc.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 11:42:00 -0000 [thread overview]
Message-ID: <4E16EB74.2040002@gnu.org> (raw)
In-Reply-To: <yddsjqhypn5.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On 07/08/2011 01:31 PM, Rainer Orth wrote:
> And another easy one: moving libgcov over to libgcc.
>
> Bootstrapped without regressions on i386-pc-solaris2.11 and
> x86_64-unknown-linux-gnu.
>
> Ok for mainline?
>
> After this one, and once the problems with the unwinder move are sorted
> out, I've got a few more:
>
> * gthr is just in the planning stage
>
> * fp-bit is almost ready
>
> * soft-fp just started to investigate
>
> * libgcc_tm_file only an idea
>
> Rainer
>
Ok!
Paolo
next prev parent reply other threads:[~2011-07-08 11:35 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 [this message]
2011-07-08 14:35 ` Joseph S. Myers
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=4E16EB74.2040002@gnu.org \
--to=bonzini@gnu.org \
--cc=Ralf.Wildenhues@gmx.de \
--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).