Re: Unmark pdumped objects
On Tue, Oct 26, 1999 at 11:11:28AM -0700, Martin Buchholz wrote:
It used to be, when you build XEmacs in debug mode, that it would
print out the sizes of things, including byte-code stuff, when it
dumped. Olivier, you could try building one of those ancient
pre-pdump XEmacsen and see what happens. That sort of information
*is* useful for core C developers such as yourself.
Sure it is. But it was printing _purespace_ stats only. I'm thinking
abour writing a subr that could give a vector with this kind of
information at any time. I'm interessed by the object uses when
running real applications too, not only at dump time.
The original bytecode string is discarded (and
``re-constructed'' when
the user calls compiled-function-instructions or disassemble), so
there is effectively NO extra space used, in fact there may be a
slight saving in space when the original compiled function
instructions are (hopefully) garbage collected.
Of course, I don't dump what is not referenced. I'm going to compile
with and without systematic o-c-f and compare the size of xemacs.dmp.
OG.