Reason for cygwin GCC 2.97 non-bootstrap found
DJ Delorie
dj@delorie.com
Mon Nov 20 20:42:00 GMT 2000
> 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 cygwin-unsubscribe@sourceware.cygnus.com
More information about the Cygwin
mailing list