Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Date: Mon, 20 Nov 2000 23:01:30 -0500
Message-Id: <200011210401.XAA10968@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj@envy.delorie.com using -f
From: DJ Delorie <dj@delorie.com>
To: rth@redhat.com
CC: zackw@Stanford.EDU, Kelley.Cook@home.com, Cygwin@sources.redhat.com,
        gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org
In-reply-to: <20001120194446.A17399@redhat.com> (message from Richard
	Henderson on Mon, 20 Nov 2000 19:44:46 -0800)
Subject: Re: Reason for cygwin GCC 2.97 non-bootstrap found
References: <200011202245.eAKMjjN27680@plmlir3.mail.eds.com> <20001120154222.O17712@wolery.stanford.edu> <20001120192414.D17317@redhat.com> <20001120193449.Y17712@wolery.stanford.edu> <20001120194446.A17399@redhat.com>


> IMO there's no pressing reason to do _any_ of it in libiberty,

The original patches included an implementation of valloc() in
libiberty, for systems that didn't have one, so that ggc could rely on
a working valloc.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com