#1120: [CAGE] More rigorous testing for constant tables across threads
---------------------+------------------------------------------------------
Reporter: allison | Owner:
Type: cage | Status: new
Priority: normal | Milestone:
Component: none | Version: 1.6.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Description changed by allison:
Old description:
> With the merge of the pcc_reapply branch, test 13 in t/pmc/threads.t will
> have 3 sections commented out. These sections depend on a sub in the
> constants table being the same as the sub stored in the namespace. This
> is true for the main interpreter, but not always true for a thread.
>
> Need more extensive testing of the constants table in threads. It could
> be argued that the constants table should be cloned, or that even direct
> sub access should be doing a lookup in the namespace for accuracy (with a
> possible hit in speed).
New description:
With the merge of the pcc_reapply branch, test 13 in t/pmc/threads.t will
have 3 sections commented out (from r41939). These sections depend on a
sub in the constants table being the same as the sub stored in the
namespace. This is true for the main interpreter, but not always true for
a thread.
Need more extensive testing of the constants table in threads. It could be
argued that the constants table should be cloned, or that even direct sub
access should be doing a lookup in the namespace for accuracy (with a
possible hit in speed).
--
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1120#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
