Dan Sugalski wrote:
>
> At 10:41 PM -0400 5/17/02, Jeff wrote:
> >I'm about ready to commit the fixes to the current assembler, which will
> >finally make proper keyed aggregate access ready. Looking at the test
> >suite, I see some places where we use raw opcode names, such as
> >'ne_n_nc_ic'. I
At 10:41 PM -0400 5/17/02, Jeff wrote:
>I'm about ready to commit the fixes to the current assembler, which will
>finally make proper keyed aggregate access ready. Looking at the test
>suite, I see some places where we use raw opcode names, such as
>'ne_n_nc_ic'. It appears to be random, and I'd l
I'm about ready to commit the fixes to the current assembler, which will
finally make proper keyed aggregate access ready. Looking at the test
suite, I see some places where we use raw opcode names, such as
'ne_n_nc_ic'. It appears to be random, and I'd like to know if keeping
the ability to acces