Mailing-List: contact issues-help@systemml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@systemml.apache.org
Date: Wed, 13 Dec 2017 00:04:00 +0000 (UTC)
From: "Matthias Boehm (JIRA)" <jira@apache.org>
To: issues@systemml.apache.org
Message-ID: <JIRA.13124531.1513123238000.443810.1513123440164@Atlassian.JIRA>
In-Reply-To: <JIRA.13124531.1513123238000@Atlassian.JIRA>
References: <JIRA.13124531.1513123238000@Atlassian.JIRA> <JIRA.13124531.1513123238450@jira-lw-us.apache.org>
Subject: [jira] [Updated] (SYSTEMML-2050) Prints show in reverse order of
 merge of statement blocks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 13 Dec 2017 00:04:04 -0000


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

Matthias Boehm updated SYSTEMML-2050:
-------------------------------------
    Description: 
As pointed out by [~dusenberrymw] - prints currently show up in reverse order after the merge of sequences of statement blocks. For instance, the following example 

{code}
print("test1");
print("test"+2);
print("test"+3);
if(1==1){} 
print("test4");
print("test"+5);
{code}

currently produces the following output

{code}
test4
test5
test1
test2
test3
{code}

The new instruction scheduling introduced with SYSTEMML-2039 ensures (as a byproduct) that prints within one DAG are scheduled in their original order. However, after the merge of statement blocks, prints without data dependencies can be reordered. 

This task aims to simply sort all DAG output instructions accordingly to their line numbers. Note that his only affects the new instruction scheduling as used for spark, hybrid_spark, and singlenode.

  was:
As pointed out by [~dusenberrymw] - prints currently show up in reverse order after the merge of sequences of statement blocks. For instance, the following example 

{code}
print("test1");
print("test"+2);
print("test"+3);
if(1==1){} 
print("test4");
print("test"+5);
{code}

currently produces the following output

{code}
test4
test5
test1
test2
test3
{code}

The new instruction scheduling introduced with SYSTEMML-2039 ensures (as a byproduct) that prints within one DAG are scheduled in their original order. However, after the merge of statement blocks, prints without data dependencies can be reordered. 

This task aims to simply sort all DAG output instructions accordingly to their line numbers.


> Prints show in reverse order of merge of statement blocks
> ---------------------------------------------------------
>
>                 Key: SYSTEMML-2050
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-2050
>             Project: SystemML
>          Issue Type: Bug
>            Reporter: Matthias Boehm
>
> As pointed out by [~dusenberrymw] - prints currently show up in reverse order after the merge of sequences of statement blocks. For instance, the following example 
> {code}
> print("test1");
> print("test"+2);
> print("test"+3);
> if(1==1){} 
> print("test4");
> print("test"+5);
> {code}
> currently produces the following output
> {code}
> test4
> test5
> test1
> test2
> test3
> {code}
> The new instruction scheduling introduced with SYSTEMML-2039 ensures (as a byproduct) that prints within one DAG are scheduled in their original order. However, after the merge of statement blocks, prints without data dependencies can be reordered. 
> This task aims to simply sort all DAG output instructions accordingly to their line numbers. Note that his only affects the new instruction scheduling as used for spark, hybrid_spark, and singlenode.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)