Skip to content

non-BE conformance--fix intersect 1d RAM usage issue

  • Related issues:
  • Requested reviewers:

Reason why this change is needed

  • Intersect 1D uses large RAM size as the buffers are too big.
  • breaking intersect1d into sub steps.

Description of the change

  • Describe what is done.

Affected operating points

  • Describe here as well as possible what operating points are affected and how
  • In minimum, there should be a status for bitstream compatibility and output bit exactness
  • For bitstream compatibility, the following levels are helpful for describing encoder
    1. Produced bitstream is BE compared to previous state.
    2. Produced bitstream is non-BE but it is fully backwards compatible for decoding. Decoded output may differ.
    3. Produced bitstream is non-BC. Old decoder cannot decode the produced bitstream correctly.
  • For output difference, use BE or non-BE. Additionally, amount of difference can be presented.

Merge request reports

Loading