Jason --
> Making the distinction between the three cases enables a number of
> optimizations of native code based on analysing data flow. 'in' would be good
> as an implicit default, as many PMC opcodes will not overwrite any PMC
> registers.
>
> An optimizing native code generator (whether st
On Mon, Dec 24, 2001 at 02:11:15PM -0500, Gregor N. Purdy wrote:
> Or, do we really need to have the three-way in/out/inout tagset?
>
> inline op set(out i, in i|ic) {
> $1 = $2;
> }
Making the distinction between the three cases enables a number of
optimizations of native code based on
On Mon, Dec 24, Gregor N. Purdy wrote:
> Nicholas --
>
> > Parrot_set_i_i(in,out): \x8b \x0d &IR2 \x89 \x0d &IR1
>
> I'm tempted to push the specification of this information all the way
> back to the syntax of .ops files, since the code that lives there
> should behave the same wrt read/write o
Gregor N. Purdy:
# > Parrot_set_i_i(in,out): \x8b \x0d &IR2 \x89 \x0d &IR1
#
# I'm tempted to push the specification of this information all the way
# back to the syntax of .ops files, since the code that lives there
# should behave the same wrt read/write on args.
#
# Dan likes C-like syntax as m
