This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Add BeOS support for libstdc++-v3
- To: Jason Merrill <jason at redhat dot com>
- Subject: Re: [PATCH] Add BeOS support for libstdc++-v3
- From: Daniel Berlin <dberlin at cygnus dot com>
- Date: Fri, 24 Nov 2000 12:51:01 -0800 (PST)
- cc: Gabriel Dos Reis <gdr at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
On Fri, 24 Nov 2000, Jason Merrill wrote:
> >>>>> "Daniel" == Daniel Berlin <dberlin@redhat.com> writes:
>
> > I know, it's actually something I noticed in V2. Because libroot is a
> > bastardized glibc, it doesn't identify itself as GLIBC, but a lot of
> > functionality from glibc is there, including the locking bits. Not enough
> > that you can get away with saying it's GLIBC 2.1, too much thinks that
> > means we have things we don't.
>
> > It's a serious pain in the ass on BeOS.
>
> Yep. Unfortunately, Be insisted that we tear all that stuff out; I
> believe they felt this was necessary to reduce the footprint of the
> library, because BeOS doesn't have demand paging.
Err, unless i've got the definition of demand paging wrong (it's
possible, baby rabbits keepint me up all night digging at the metal
cage), it certainly does.
It might not have had it when the port was originally done, however.
I've floated the idae of moving to glibc 2.2, since it would be more
maintainable to use a port than a bastardized obsolete version. It took
me about a week to get glibc 2.2 going on BeOS nicely. Friends at Be who
ran the idea past management said it was met lukewarmly, to put it
kindly. THey see no reason to use antyihg but what they have (I had
already run down the list of advantages for them).
--Dan
> Jason >