At 06:30 PM 1/6/2002 -0800, Hong Zhang wrote:
> > 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
> 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 -
At 09:59 PM 1/4/2002 -0600, David M. Lloyd wrote:
>That's what I thought I remembered; in that case, here's a patch:
Applied, thanks.
Dan
--"it's like this"---
Dan Sugalski even
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 in
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 i
I'm getting warnings on this bit of core.ops when compiling with 64-bit
ints:
op write(i|ic, i|ic) {
INTVAL * i = &($2); /* */
write($1, i, sizeof(INTVAL));
goto NEXT();
}
I'm getting a warning that stems from the fact that sizeof(INTVAL) = 8 and
sizeof(opcode_t) = 4, so the poi
