You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2018/02/06 20:34:00 UTC

[jira] [Closed] (DAFFODIL-1767) byteOrderChangeParser optimization not working

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

Michael Beckerle closed DAFFODIL-1767.
--------------------------------------
    Resolution: Won't Fix
      Assignee: Dave Thompson  (was: Michael Beckerle)

Code is gone. That is, there are no more byteOrderChangeParsers, so this bug is no longer relevant.

> byteOrderChangeParser optimization not working
> ----------------------------------------------
>
>                 Key: DAFFODIL-1767
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1767
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Middle &quot;End&quot;
>            Reporter: Michael Beckerle
>            Assignee: Dave Thompson
>            Priority: Major
>             Fix For: 2.1.0
>
>
> If you run TestChoice1765.test_backtrack1 with trace on (modify to have runner.trace.runOneTest(...) ), you see lots of byte order change parsers executing.
> But the schema has globally byteOrder="bigEndian" so there should only be one byteOrderChange parser to set it once and for all at the start of the whole thing. The others should optimize away.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)