Ticket #1025 (closed RFC: fixed)
PASM Registers limited to 2 digits.
Reported by: | coke | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | none | Version: | |
Severity: | medium | Keywords: | |
Cc: | Language: | ||
Patch status: | Platform: |
Description
See the Original RT.
Currently PASM registers are limited to 2 digits. That is, P99 is a valid register, but P999 is not.
PIR maps the large numbers to "physical" parrot registers; I claim in the original RT that this same mapping should apply to PASM registers, but: I cannot find the reference to support this, and parrot -t1 output shows that P99 uses register # 99.
So, this needs an architectural decision; Should PASM do a similar arbitrary mapping of register numbers? If so, code needs fixing.
If not, the test in t/compilers/syn/regressions.t for PASM needs to be removed, the docs need to be updated to indicate there is a hard limit for PASM registers, (and we might want to decide if we want that hard limit increased, as it's currently 100)