From 69c7ad340721e9ca3659af054808c10aa91980df Mon Sep 17 00:00:00 2001 From: hui su Date: Thu, 7 Apr 2016 11:04:40 -0700 Subject: Correct comments for scan order neighbors Change-Id: I5e2dc39bf0ee8e501e4dd358be2e92ae50934593 --- vp9/common/vp9_scan.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'vp9/common/vp9_scan.c') diff --git a/vp9/common/vp9_scan.c b/vp9/common/vp9_scan.c index d6fb8b2d7..8b8b09f4a 100644 --- a/vp9/common/vp9_scan.c +++ b/vp9/common/vp9_scan.c @@ -229,10 +229,8 @@ DECLARE_ALIGNED(16, static const int16_t, default_scan_32x32[1024]) = { 990, 959, 1022, 991, 1023, }; -// Neighborhood 5-tuples for various scans and blocksizes, -// in {top, left, topleft, topright, bottomleft} order -// for each position in raster scan order. -// -1 indicates the neighbor does not exist. +// Neighborhood 2-tuples for various scans and blocksizes, +// in {top, left} order for each position in corresponding scan order. DECLARE_ALIGNED(16, static const int16_t, default_scan_4x4_neighbors[17 * MAX_NEIGHBORS]) = { 0, 0, 0, 0, 0, 0, 1, 4, 4, 4, 1, 1, 8, 8, 5, 8, 2, 2, 2, 5, 9, 12, 6, 9, -- cgit v1.2.3