Dan Sugalski [EMAIL PROTECTED] wrote:
It's possible to get the register allocator in what is essentially an
infinite loop, where it runs forever or until it blows memory and
dies. It needs to have a means to check for too many iterations and
fall back to a slow-but-working version with too
At 9:43 AM +0200 5/25/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
It's possible to get the register allocator in what is essentially an
infinite loop, where it runs forever or until it blows memory and
dies. It needs to have a means to check for too many iterations and
Dan Sugalski [EMAIL PROTECTED] wrote:
I can see that helping in some circumstances (though not mine) but
the code that the register allocator's having fits with has no .local
declarations at all. It's all $x register usage from beginning to end.
Don't you have something like variables, which
At 4:29 PM +0200 5/25/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
I can see that helping in some circumstances (though not mine) but
the code that the register allocator's having fits with has no .local
declarations at all. It's all $x register usage from beginning to end.
# New Ticket Created by Dan Sugalski
# Please include the string: [perl #29837]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=29837
It's possible to get the register allocator in what is essentially an
infinite
