> The point being? There's _still_ no reason it _must_ be done > in libiberty. No, but a generic valloc would make sense in libiberty. If the final solution includes a generic valloc implementation, it might make more sense to put that in libiberty rather than gcc. You're right that it's not a *pressing* reason, but it is something to consider. -- Want to unsubscribe from this list? Send a message to [EMAIL PROTECTED]
- Re: Reason for cygwin GCC 2.97 non-bootstrap fo... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-bootstr... Christopher Faylor
- Re: Reason for cygwin GCC 2.97 non-boo... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non... Christopher Faylor
- Re: Reason for cygwin GCC 2.97... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-bootstr... Richard Henderson
- Re: Reason for cygwin GCC 2.97 non-boo... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non... Richard Henderson
- Re: Reason for cygwin GCC 2.97... DJ Delorie
- Re: Reason for cygwin GCC... Richard Henderson
- Re: Reason for cygwin... DJ Delorie
- Re: Reason for cygwin GCC 2.97 non-bootstrap fo... Kelley Cook
- Re: Reason for cygwin GCC 2.97 non-bootstr... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-boo... Phil Edwards
- Re: Reason for cygwin GCC 2.97 non... Zack Weinberg
- Re: Reason for cygwin GCC 2.97... Chris Abbey
- Re: Reason for cygwin GCC... Zack Weinberg
- Re: Reason for cygwin GCC 2.97... Phil Edwards
- Re: Reason for cygwin GCC 2.97 non-boo... DJ Delorie
- RE: Reason for cygwin GCC 2.97 non-bootstrap fo... Billinghurst, David (CRTS)
- Re: Reason for cygwin GCC 2.97 non-bootstrap fo... McNulty Junior Bobby
