delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com> |
List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, |
<http://sourceware.cygnus.com/ml/#faqs> | |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
From: | Sigbjorn Finne <sof AT dcs DOT gla DOT ac DOT uk> |
To: | cygwin AT sourceware DOT cygnus DOT com |
Subject: | dlltool & memory hoggage |
Date: | Wed, 4 Aug 1999 20:27:34 +0100 (BST) |
Message-Id: | <14248.37926.416595.443625@hawaii> |
X-Mailer: | VM 6.64 under Emacs 19.34.1 |
MIME-Version: | 1.0 |
Hi, I wondered whether anyone's had a look at why dlltool consumes so much VM when executing? When building DLLs with 100s (and in some cases 1000s) of exported entry points, I'm seeing images that often are > 50M in size (this is with both B20.1's dlltool.exe and one built from the latest binutils src snapshot.) Before I have a go at trying to chase this one down, I'd be very interested to hear from people that have investigated this one already and what the findings were. thanks, --sigbjorn -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |