tree 970519a7825586c49c94605ae99d5ddb497dc741
parent df5b2915d58a5da341871c7f7c251f92328f9587
author David Barker <david.barker@argondesign.com> 1521470331 +0000
committer Debargha Mukherjee <debargha@google.com> 1521515016 +0000

[NORMATIVE] Check primary_ref_frame in more places

There are a few cases where we should treat frames with
primary_ref_frame == PRIMARY_REF_NONE the same way as intra-only
and/or error-resilient frames, even if the frame of interest
is neither intra-only nor error resilient.

Note, however, that they shouldn't be treated the same in all cases.

This patch changes the following cases:

* Always signal segmentation map + features when using PRIMARY_REF_NONE

* Call setup_past_independence() when using PRIMARY_REF_NONE, so that
  we don't accidentally depend on old data. This should be equivalent
  to the old behaviour, but makes it less likely to miss anything
  in future.

* Simplify some code using the fact that, once cm->prev_frame has
  been set up, the following are all equivalent:
  "cm->prev_frame == NULL";

  "cm->primary_ref_frame == PRIMARY_REF_NONE";

  "cm->error_resilient_mode || cm->intra_only ||
   [primary_ref_frame explicitly signalled as PRIMARY_REF_NONE]"

Change-Id: If8e417a11040ba8a4ad58fc6e37d985a94533d68