Rhys Weatherley wrote:
Leopold Toetsch wrote:
[ imcc ]
Yes, I saw that. I haven't yet decided whether to generate pasm or imcc directly from cscc. I did have some problems getting "test_spilling.imc" to work. Is this a known issue?
Now yes ;-) Last cleanup changes did break the spilling code. I've got it running again, though there are still minor issues.
I'll commit it in a minute.
int x = (0x80000000 + 0x80000000) / 2; This will give 0 on a 32-bit system, but 0x80000000 on a 64-bit.
No, this would be done in your integer class.
Note: I'm not criticising Parrot's choice to use native integers.
Native integers are for HL languages, that know the limitations or for fast packed arrays and such.
All the rest (including sign extension) could go in extra classes.
Though, on popular demand, there could be some opcodes for e.g. int<->short conversions.
[ bytecode ]
I have a suggestion: allow compilers to embed arbitrary extra
"named sections" in the bytecode format.
Yes, that was my proposal too.
Cheers, Rhys.
leo
