On Fri, 4 Jan 2002, Bryan C. Warnock wrote: > On Friday 04 January 2002 10:43 pm, David M. Lloyd wrote: > > > > So that you can use constants that are up to sizeof(opcode_t) bytes, but > > after that you're on your own. That raises a question, though: Do we > > want to move integer constants into the constant table? > > We're guaranteeing 32 bits of inline integer arguments. If integers > (or/and) opcodes are 64 bits, we're only guaranteeing the LS 32 bits. > Anything larger needs to be a PMC.
That's what I thought I remembered; in that case, here's a patch: Index: core.ops =================================================================== RCS file: /home/perlcvs/parrot/core.ops,v retrieving revision 1.68 diff -u -r1.68 core.ops --- core.ops 4 Jan 2002 02:36:25 -0000 1.68 +++ core.ops 5 Jan 2002 03:58:14 -0000 @@ -463,8 +463,8 @@ =cut op write(i|ic, i|ic) { - INTVAL * i = &($2); - write($1, i, sizeof(INTVAL)); + INTVAL i = (INTVAL)$2; + write($1, &i, sizeof(INTVAL)); goto NEXT(); } - D <[EMAIL PROTECTED]>