You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2021/05/20 20:02:04 UTC

[jira] [Closed] (DAFFODIL-830) Performance: Remove unnecessary SeqCombParsers from generated parser

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

Dave Thompson closed DAFFODIL-830.
----------------------------------

Closing due to no activity.
The specified commit was in the latest pull from the daffodil repository.
The code was peer reviewed per process.
If an issue occurs with the updates it will be addressed in a new tickets.

> Performance: Remove unnecessary SeqCombParsers from generated parser
> --------------------------------------------------------------------
>
>                 Key: DAFFODIL-830
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-830
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Middle &quot;End&quot;, Performance
>    Affects Versions: s10
>            Reporter: Mike Beckerle
>            Assignee: Dave Thompson
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> This is another missing optimization.
> We often have parsers that have nested <seq>....</seq>
> This is never needed as these can be merged. This improves tracing and debugging by avoiding having these excess things there.
> It also simply reduces the number of parser 'actions' a bit, so can't hurt for performance reasons. Every parsed element seems to have at least one excess <seq>...</seq> created around it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)