On Wed, Nov 23, 2011 at 04:00:58PM +1300, Michael Hope wrote:
> On Tue, Nov 22, 2011 at 12:10 AM, Dave Martin wrote:
> > Defining a macro seems to eat up about half a megabyte of memory,
> > due to the excessively large size of the macro arguments hash table
> > (large enough for 65537 entries by
On Tue, Nov 22, 2011 at 12:10 AM, Dave Martin wrote:
> Defining a macro seems to eat up about half a megabyte of memory,
> due to the excessively large size of the macro arguments hash table
> (large enough for 65537 entries by default).
Hi Dave. Just bikshedding responses from me, but that's be
Defining a macro seems to eat up about half a megabyte of memory,
due to the excessively large size of the macro arguments hash table
(large enough for 65537 entries by default).
As a result, gas memory consumption becomes rather huge when a
modestly large number (hundreds) of macros are defined.
I discovered some excessive memory usage in gas recently when
defining macros. It turns out that this is a weird implementation
feature rather than a bug.
This patch has a possible fix for the issue, but I'd be interested
in people's views before I go so far as cleaning it up and
discussing it up
