HTTP/1.1 -1 Read error in cache disk data: SuccessContent-Type: text/tab-separated-values; charset="utf-8" Last-Modified: Sat, 22 Jan 2022 03:48:59 GMT Content-length: 1054 Connection: Close Proxy-Connection: Close X-Cache: HIT from web1.osuosl.org Server: ProxyTrack 0.5 (HTTrack 3.49.2) id summary reporter owner description type status priority milestone component version severity resolution keywords cc lang patch platform 1025 PASM Registers limited to 2 digits. coke "See the [http://rt.perl.org/rt3/Ticket/Display.html?id=41788 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)" RFC closed minor none medium fixed chrome/com