systemml-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Boehm (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SYSTEMML-1459) Wrong codegen materialization decisions due to dangling hop parents
Date Wed, 05 Apr 2017 01:26:41 GMT

     [ https://issues.apache.org/jira/browse/SYSTEMML-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matthias Boehm updated SYSTEMML-1459:
-------------------------------------
    Description: 
The cost-based codegen plan selector uses hops with multiple consumers as candidates for decisions
on materalization points. On end-to-end algorithm scenarios, we encountered side effects from
specific dynamic simplification rewrites which did not properly cleanup parent-child pointers
of removed hops.

Additionally, the rewrite fuseBinarySubDAGToUnaryOperation showed issues due to multiple applied
pattern, where the first pattern modified the dag, but the second pattern matched against
the original dag structure and hence together these rewrites create a wrong modified output
DAG. 

  was:The cost-based codegen plan selector uses hops with multiple consumers as candidates
for decisions on materalization points. On end-to-end algorithm scenarios, we encountered
side effects from specific dynamic simplification rewrites which did not properly cleanup
parent-child pointers of removed hops.


> Wrong codegen materialization decisions due to dangling hop parents
> -------------------------------------------------------------------
>
>                 Key: SYSTEMML-1459
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-1459
>             Project: SystemML
>          Issue Type: Bug
>            Reporter: Matthias Boehm
>            Assignee: Matthias Boehm
>             Fix For: SystemML 1.0
>
>
> The cost-based codegen plan selector uses hops with multiple consumers as candidates
for decisions on materalization points. On end-to-end algorithm scenarios, we encountered
side effects from specific dynamic simplification rewrites which did not properly cleanup
parent-child pointers of removed hops.
> Additionally, the rewrite fuseBinarySubDAGToUnaryOperation showed issues due to multiple
applied pattern, where the first pattern modified the dag, but the second pattern matched
against the original dag structure and hence together these rewrites create a wrong modified
output DAG. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message