139 10001011 kkkkkkkk jjjjjjjj Invoke primitive number
jjjjjjjjkkkkkkkk
140 10001100 kkkkkkkk jjjjjjjj Push Temp At kkkkkkkk In
Temp Vector At: jjjjjjjj 141 10001101 kkkkkkkk jjjjjjjj Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj 142 10001110 kkkkkkkk jjjjjjjj Pop and Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj 143 10001111 llllkkkk jjjjjjjj iiiiiiii Push Closure Num Copied llll Num Args kkkk BlockSize jjjjjjjjiiiiiiii
Why is the primitive index in bytecode 139 stored little-endian? The other bytecodes with immediate args > 8 bits are in big endian (e.g. push closure copy)
- Bert -
On Fri, Jul 8, 2016 at 2:00 AM, Bert Freudenberg bert@freudenbergs.de wrote:
139 10001011 kkkkkkkk jjjjjjjj Invoke primitive number
jjjjjjjjkkkkkkkk
140 10001100 kkkkkkkk jjjjjjjj Push Temp At kkkkkkkk In
Temp Vector At: jjjjjjjj 141 10001101 kkkkkkkk jjjjjjjj Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj 142 10001110 kkkkkkkk jjjjjjjj Pop and Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj 143 10001111 llllkkkk jjjjjjjj iiiiiiii Push Closure Num Copied llll Num Args kkkk BlockSize jjjjjjjjiiiiiiii
Why is the primitive index in bytecode 139 stored little-endian? The other bytecodes with immediate args > 8 bits are in big endian (e.g. push closure copy)
No reason beyond my habit and preference.
_,,,^..^,,,_ best, Eliot
On Sat, Jul 9, 2016 at 12:29 AM, Eliot Miranda eliot.miranda@gmail.com wrote:
On Fri, Jul 8, 2016 at 2:00 AM, Bert Freudenberg bert@freudenbergs.de wrote:
139 10001011 kkkkkkkk jjjjjjjj Invoke primitive number
jjjjjjjjkkkkkkkk
140 10001100 kkkkkkkk jjjjjjjj Push Temp At kkkkkkkk In
Temp Vector At: jjjjjjjj 141 10001101 kkkkkkkk jjjjjjjj Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj 142 10001110 kkkkkkkk jjjjjjjj Pop and Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj 143 10001111 llllkkkk jjjjjjjj iiiiiiii Push Closure Num Copied llll Num Args kkkk BlockSize jjjjjjjjiiiiiiii
Why is the primitive index in bytecode 139 stored little-endian? The other bytecodes with immediate args > 8 bits are in big endian (e.g. push closure copy)
No reason beyond my habit and preference.
Can we still fix it? It seems really weird to me to have two different conventions in one bytecode set.
- Bert -
squeak-dev@lists.squeakfoundation.org