#452: [TODO] Don't use MULTI when not needed
---------------------+------------------------------------------------------
Reporter: allison | Owner: cotto
Type: todo | Status: assigned
Priority: normal | Milestone: 1.4
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by bacek):
Replying to [comment:1 chromatic]:
> For now I'd rather see the PMC parser and code generator improved so
that we can add an optimization to collapse "unnecessary" MULTIs into
if/else statements. We can undo that optimization as needed. This would
allow us to keep the source code of PMCs reasonably clear in terms of
intended semantics while taking advantage of short term optimizations and
waiting for longer term optimizations.
Collapsing VABLE creation implemented in r39253. Now we can undo that
optimisation if needed.
Only one unexpected failure for dynpmc/foo dispatch. I'll fix it later
today by generating proper VTABLE function for dynpmc.
--
Bacek
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/452#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
