Re: class gc and gc_alloc(0, xxx)

From: Godmar Back (gback@cs.utah.edu)
Date: Fri Dec 18 1998 - 10:51:57 EST

• Next message: Godmar Back: "[CVS] commit"
• Previous message: Godmar Back: "[CVS] commit"
• In reply to: Parmelan, Edouard: "class gc and gc_alloc(0, xxx)"
• Next in thread: Archie Cobbs: "Re: class gc and gc_alloc(0, xxx)"
• Reply: Archie Cobbs: "Re: class gc and gc_alloc(0, xxx)"

>
> I also found that READMETHODS_START() use GC_WRITE()
> but READFILES_START() don't. As GC_WRITE() is currently
> not implemented, I don't know witch one is correct.
>
>

It's correct to have it.
I have a whole list of missing GC_WRITEs which I'll put in at some
point. Implementing incremental or generational gc will be a huge
project by itself.

> The following patch:
> - don't alloc a Method array if METHODS_COUNT == 0
> [as in READFIELDS_START()].
> - add an assert(size != 0) in gcMalloc().

Yes, I think that's a good course of action.
I also added an assert if someone attempt to free non-fixed objects.

We need to stop to silently ignore things that don't hurt immediately
unless we really understand them.

>
> I forgot config/i386/linux/md.h in my -Wall patch yesterday,
> so I join it today :)

Thanks.

        - Godmar

• Next message: Godmar Back: "[CVS] commit"
• Previous message: Godmar Back: "[CVS] commit"
• In reply to: Parmelan, Edouard: "class gc and gc_alloc(0, xxx)"
• Next in thread: Archie Cobbs: "Re: class gc and gc_alloc(0, xxx)"
• Reply: Archie Cobbs: "Re: class gc and gc_alloc(0, xxx)"

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:22 EDT