Opened 4 years ago
Closed 4 years ago
#1213 closed defect (fixed)
Order of operations in Eq 352
| Reported by: | bheng | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | spec | Version: | VVC D10 vD |
| Keywords: | Cc: | ksuehring, bbross, XiangLi, fbossen, jvet@… |
Description
I believe the order of the == and & operations in Eq 352 will produce the wrong result:
bCTUboundary = ( yTbY & ( CtbSizeY − 1 ) = = 0 ) ? TRUE : FALSE
An extra set of parenthesis is probably needed.
bCTUboundary = ( ( yTbY & ( CtbSizeY − 1 ) ) = = 0 ) ? TRUE : FALSE
Change history (1)
comment:1 Changed 4 years ago by jlchen
- Resolution set to fixed
- Status changed from new to closed
Note: See TracTickets for help on using tickets.
You're right, operation "= =" has higher precedence than operation "&" in our spec. Good catch!
will include the fix in the JVET-S2001-vE release.