From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: DJ Delorie <dj@redhat.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: RFA: consolidate DWARF strings into libiberty
Date: Mon, 19 Mar 2012 16:10:00 -0000 [thread overview]
Message-ID: <CADPb22RdZoPSt9eV4b+jJHbYjNMSC=s1ZQih31+JTtrW4OJW-w@mail.gmail.com> (raw)
In-Reply-To: <871uotbscq.fsf@fleche.redhat.com>
On Thu, Mar 15, 2012 at 12:02 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "DJ" == DJ Delorie <dj@redhat.com> writes:
>
> Tom> Finally, there is already stuff in libiberty not related to
> Tom> portability. E.g., hashtab or the demangler.
>
> DJ> Yeah, I know, hence my "Should I give up that premise?"
>
> Yeah.
>
> I am not sure there will ever be enough shared code to warrant a new
> library, particularly because adding a new library is so expensive --
> not just the configury stuff but also adding it to the link lines in the
> Makefiles of all the tools that might need it.
>
> I suppose if I had my wish list implemented here, it would be to remove
> the portability stuff from libiberty in favor of gnulib, and keep
> libiberty as a higher-level library.
That won't really fix libiberty being an ever growing kitchen sink.
How hard would it really be to make it easier to add new libraries?
It's not like we're expecting 100.
But given the pushback for even one new library, I think we're
unnecessarily slowing ourselves down.
next prev parent reply other threads:[~2012-03-19 16:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 18:00 Tom Tromey
2012-03-15 18:34 ` DJ Delorie
[not found] ` <201203151833.q2FIXeOs003077__40387.7084645957$1331836457$gmane$org@greed.delorie.com>
2012-03-15 18:42 ` Tom Tromey
2012-03-15 18:49 ` DJ Delorie
2012-03-15 18:54 ` Pedro Alves
2012-03-15 19:01 ` Jakub Jelinek
[not found] ` <201203151848.q2FImnAq004284__18018.6977530413$1331837385$gmane$org@greed.delorie.com>
2012-03-15 19:02 ` Tom Tromey
2012-03-19 16:10 ` Doug Evans [this message]
2012-03-19 16:14 ` DJ Delorie
[not found] ` <201203191613.q2JGCx5m011858__41727.2307830446$1332173667$gmane$org@greed.delorie.com>
2012-03-19 17:25 ` Tom Tromey
[not found] ` <87obrsmrma.fsf__45145.0892644518$1332177916$gmane$org@fleche.redhat.com>
2012-03-30 18:57 ` Tom Tromey
2012-04-05 19:29 ` Tom Tromey
2012-04-13 19:57 ` Tom Tromey
[not found] ` <87d37bwgq1.fsf__11149.6676145636$1334346880$gmane$org@fleche.redhat.com>
2012-04-23 14:51 ` Tom Tromey
2012-04-26 15:04 ` Jakub Jelinek
2012-04-26 18:26 ` DJ Delorie
2012-04-26 21:15 ` Jakub Jelinek
[not found] ` <20120426203911.GC16117__46696.8788685792$1335472814$gmane$org@tyan-ft48-01.lab.bos.redhat.com>
2012-04-27 14:17 ` Tom Tromey
2012-04-27 16:02 ` H.J. Lu
2012-04-27 16:04 ` H.J. Lu
2012-04-27 16:12 ` Tom Tromey
2012-04-27 17:29 ` Tom Tromey
2012-03-19 22:49 ` Doug Evans
[not found] ` <20120315190113.GB16117__13472.8689365604$1331838115$gmane$org@tyan-ft48-01.lab.bos.redhat.com>
2012-03-15 19:04 ` Tom Tromey
2012-03-15 19:30 ` Tom Tromey
2012-03-16 21:26 ` Richard Henderson
2012-04-07 14:02 ` nick clifton
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='CADPb22RdZoPSt9eV4b+jJHbYjNMSC=s1ZQih31+JTtrW4OJW-w@mail.gmail.com' \
--to=dje@google.com \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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