pure storage overflow with DENABLE_CHECKING

pure storage overflow with DENABLE_CHECKING

[Chong Yidong]

I just noticed that when Emacs is compiled with DENABLE_CHECKING, the
following warning message pops up:

  emacs:0:Pure Lisp storage overflow (approx. 1338624 bytes needed)
  8912 pure bytes used

(There is no problem if one compiles without DENABLE_CHECKING).

Re: pure storage overflow with DENABLE_CHECKING

[Miles Bader]

Chong Yidong <cyd@stupidchicken.com> writes:
> I just noticed that when Emacs is compiled with DENABLE_CHECKING, the
> following warning message pops up:
>
>   emacs:0:Pure Lisp storage overflow (approx. 1338624 bytes needed)
>   8912 pure bytes used

I have to bump pure-space on my personal branch too, so it seems that
the value on the trunk is quite close to overflowing.

-Miles
-- 
We are all lying in the gutter, but some of us are looking at the stars.
-Oscar Wilde

Re: pure storage overflow with DENABLE_CHECKING

[Eli Zaretskii]

> From: Miles Bader <miles.bader@necel.com>
> Date: Thu, 16 Mar 2006 12:52:19 +0900
> Cc: emacs-devel@gnu.org
> 
> Chong Yidong <cyd@stupidchicken.com> writes:
> > I just noticed that when Emacs is compiled with DENABLE_CHECKING, the
> > following warning message pops up:
> >
> >   emacs:0:Pure Lisp storage overflow (approx. 1338624 bytes needed)
> >   8912 pure bytes used
> 
> I have to bump pure-space on my personal branch too, so it seems that
> the value on the trunk is quite close to overflowing.

Not necessarily.  This could be solved by having ENABLE_CHECKING and
your branch increase pure storage size.

Re: pure storage overflow with DENABLE_CHECKING

[Ken Raeburn]

> I just noticed that when Emacs is compiled with DENABLE_CHECKING, the
> following warning message pops up:
>
>   emacs:0:Pure Lisp storage overflow (approx. 1338624 bytes needed)
>   8912 pure bytes used
>
> (There is no problem if one compiles without DENABLE_CHECKING).

That's a bit surprising ... I wasn't aware that ENABLE_CHECKING  
controlled any code that would influence the amount of pure lisp  
storage used.  It mainly enables the assertion checks done in the  
XCONS/XSTRING/XSYMBOL/etc macros and elsewhere.  In fact, I'd argue  
that if ENABLE_CHECKING is changing the amount of pure Lisp storage  
used, it's probably a bug.

Ken