Am Mittwoch, 1. August 2007 00:39 schrieb Bram Geron:
> Leopold Toetsch wrote:
> > It might be on the stack or just in a CPU register. While we have
> > code to mark all possible pointers on the stack, this isn't generally
> > true for CPU registers, as that's rather system-dependent.
> >
> > See a
Leopold Toetsch wrote:
> It might be on the stack or just in a CPU register. While we have
> code to mark all possible pointers on the stack, this isn't generally
> true for CPU registers, as that's rather system-dependent.
>
> See also src/cpu_dep.c():trace_system_areas()
If we can't rely on trac
Am Donnerstag, 19. Juli 2007 19:16 schrieb chromatic:
> >
> > The problem is as follows:
> >
> > 1) PObj_custom_mark_SET(SELF);
> > 2) counter = pmc_new(INTERP, enum_class_Integer);
> > 3) PMC_data(SELF) = counter;
> >
> > In 1) you enable marking. 2) might cause a garbage collection, while the
> >
chromatic writes:
On Thursday 19 July 2007 01:56:21 Leopold Toetsch wrote:
Am Donnerstag, 19. Juli 2007 02:48 schrieb Will Coleda:
> void init() {
> PMC* counter;
>
> PMC_str_val(SELF) =
> string_make_empty(INTERP, enum_stringrep_one, 0);
> PObj_
On Thursday 19 July 2007 01:56:21 Leopold Toetsch wrote:
> Am Donnerstag, 19. Juli 2007 02:48 schrieb Will Coleda:
> > void init() {
> > PMC* counter;
> >
> > PMC_str_val(SELF) =
> > string_make_empty(INTERP, enum_stringrep_one, 0);
> > PObj_custom_mar
Am Donnerstag, 19. Juli 2007 02:48 schrieb Will Coleda:
> I am trying to write a PMC version of PGE::CodeString, and while I
> have a PMC now that passes all the old tests, I get GC errors during
> the build process for TGE & JSON.
>
> I know they are GC related because running the affected ste
I am trying to write a PMC version of PGE::CodeString, and while I
have a PMC now that passes all the old tests, I get GC errors during
the build process for TGE & JSON.
I know they are GC related because running the affected steps with -
G, and they complete normally.
I was unable to find
