forked from AOMediaCodec/libavif
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Check if it is safe to call libyuv or libsharpyuv
The width, height, and stride parameters of libyuv and libsharpyuv functions are all of the int type. The corresponding fields in libavif are of the uint32_t type. So we need to check if it is safe to pass the libavif uint32_t values to libyuv and libsharpyuv. Related to AOMediaCodec#2271.
- Loading branch information
1 parent
47f154a
commit 9ffaae2
Showing
2 changed files
with
32 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters