Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DAFFODIL-1767

byteOrderChangeParser optimization not working

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 2.1.0
    • Component/s: Middle "End"
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              dfthompson Dave Thompson
              Reporter:
              mbeckerle Michael Beckerle
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: