Re: [PATCH] Computed goto detected at Configure.pl

2001-11-15 Thread Daniel Grunblatt
Yes, that's what the patch already does, see: opcode_t * cg_core(opcode_t *cur_opcode, struct Parrot_Interp *interpreter) { static void *ops_addr[] = { &&PC_0, &&PC_1, &&PC_2, &&PC_3, &&PC_4, PC_3: /* Parrot_close_ic */ { close(cur_opcode[1]);

Re: [PATCH] Computed goto detected at Configure.pl

2001-11-15 Thread Michael Fischer
On Thu, Nov 15, Simon Cozens wrote: > I haven't forgotten about this patch, but I've had other things going > on. I'd like to see the computed goto done as a complete state machine, > with > > goto *pc_l[(int)dest]; > > after *every single op definition* so it just jumps between labels, with

Re: [PATCH] Computed goto detected at Configure.pl

2001-11-15 Thread Simon Cozens
I haven't forgotten about this patch, but I've had other things going on. I'd like to see the computed goto done as a complete state machine, with goto *pc_l[(int)dest]; after *every single op definition* so it just jumps between labels, without any looping at all. (Apologies if that's what

Re: [PATCH] Computed goto detected at Configure.pl

2001-11-04 Thread James Mastros
On Sun, Nov 04, 2001 at 07:27:01PM -0300, Daniel Grunblatt wrote: > * A modification to Configure.pl and Makefile.in to detect if the compiler > accepts computed gotos, also added testcomputedgoto_c.in. Is there some reason that this is an _c.in file? I've noticed that both this and testparrotsiz

[PATCH] Computed goto detected at Configure.pl

2001-11-04 Thread Daniel Grunblatt
- Message Text - All.- Now I'm sending: * A modification to Configure.pl and Makefile.in to detect if the compiler accepts computed gotos, also added testcomputedgoto_c.in. * A modification to runcore_ops.c and interpreter.c adding an ifdef. * The same ops2cgc.pl and the same modificat