www.delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:1260 |
From: | wkim+@pitt.edu (Wonkoo Kim) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Why bigger exe size with LIBGRX+BCC2GRX v2.0? |
Date: | 20 Feb 1996 03:17:08 GMT |
Organization: | University of Pittsburgh |
Lines: | 13 |
Distribution: | world |
Message-ID: | <4gbefk$8u8@usenet.srv.cis.pitt.edu> |
References: | <4g3mp0$qit AT usenet DOT srv DOT cis DOT pitt DOT edu> <3128d8c4 DOT sandmann AT clio DOT rice DOT edu> |
Reply-To: | wkim+@pitt.edu (Wonkoo Kim) |
NNTP-Posting-Host: | ehdup-c1-10.rmt.net.pitt.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Thanks to DJ, Harmut, and Charles Sandmann, for their good explanations. I remember that we said v2.0 would occupy less memory by removing go32 and taking DPMI scheme. Is it still a valid statement even though libc got larger by moving some go32 functions into it? (when assuming that we had "v2.0 with go32" for the same gcc and libraries.) Thanks again. Best wishes, //-------------------------------------------------------------------- // Wonkoo Kim (wkim+@pitt.edu)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |