[perl #36407] [BUG] imcc - register allocation

1 view
Skip to first unread message

Leopold Toetsch

unread,
Jun 28, 2005, 5:21:25 AM6/28/05
to bugs-bi...@rt.perl.org
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #36407]
# in the subject line of all future correspondence about this issue.
# <URL: https://rt.perl.org/rt3/Ticket/Display.html?id=36407 >


The register allocator doesn't properly track control flow, if a label
has the same name as an opcode or a variable. The result is usually that
registers are reused because the control flow change of these labels
isn't considered.

I tried to reduce the bug to a simple example and failed. Anyway
languages/tcl/lib/commands/array.imc exposed it with labels named
'subcommand' (like a var) and 'set' (opcode).

See also r8468

leo

Bill Coffman

unread,
Jun 28, 2005, 11:14:00 AM6/28/05
to perl6-i...@perl.org
Isn't the register allocator pretty much minimized by the new architecture
implementation? My understanding was that only temporary variables could
benefit from it now. Perhaps the new changes aren't in effect yet? Just
curious.

On 6/28/05, via RT Leopold Toetsch <parrotbug...@parrotcode.org>
wrote:


--
-Bill

Leopold Toetsch

unread,
Jun 29, 2005, 2:37:42 AM6/29/05
to Bill Coffman, perl6-i...@perl.org

On Jun 28, 2005, at 17:14, Bill Coffman wrote:

> Isn't the register allocator pretty much minimized by the new
> architecture
> implementation? My understanding was that only temporary variables
> could
> benefit from it now. Perhaps the new changes aren't in effect yet? Just
> curious.

The register allocator is still the same as the final switch to the new
scheme isn't done yet.

leo

Reply all
Reply to author
Forward
0 new messages