unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* pure storage overflow with DENABLE_CHECKING
@ 2006-03-16  3:41 Chong Yidong
  2006-03-16  3:52 ` Miles Bader
  2006-03-16 10:04 ` Ken Raeburn
  0 siblings, 2 replies; 4+ messages in thread
From: Chong Yidong @ 2006-03-16  3:41 UTC (permalink / raw)


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).

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: pure storage overflow with DENABLE_CHECKING
  2006-03-16  3:41 pure storage overflow with DENABLE_CHECKING Chong Yidong
@ 2006-03-16  3:52 ` Miles Bader
  2006-03-16  4:33   ` Eli Zaretskii
  2006-03-16 10:04 ` Ken Raeburn
  1 sibling, 1 reply; 4+ messages in thread
From: Miles Bader @ 2006-03-16  3:52 UTC (permalink / raw)
  Cc: emacs-devel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: pure storage overflow with DENABLE_CHECKING
  2006-03-16  3:52 ` Miles Bader
@ 2006-03-16  4:33   ` Eli Zaretskii
  0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2006-03-16  4:33 UTC (permalink / raw)
  Cc: cyd, emacs-devel

> 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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: pure storage overflow with DENABLE_CHECKING
  2006-03-16  3:41 pure storage overflow with DENABLE_CHECKING Chong Yidong
  2006-03-16  3:52 ` Miles Bader
@ 2006-03-16 10:04 ` Ken Raeburn
  1 sibling, 0 replies; 4+ messages in thread
From: Ken Raeburn @ 2006-03-16 10:04 UTC (permalink / raw)
  Cc: emacs-devel

> 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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-03-16 10:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-16  3:41 pure storage overflow with DENABLE_CHECKING Chong Yidong
2006-03-16  3:52 ` Miles Bader
2006-03-16  4:33   ` Eli Zaretskii
2006-03-16 10:04 ` Ken Raeburn

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).