Skip to content

F
ffmpeg.wasm-core
Commit 774295a3 authored by James Almer's avatar James Almer
Browse files
Options

doc/libav-merge: mention skipped or incomplete runtime alignment commits 

Signed-off-by: 's avatarJames Almer <jamrial@gmail.com>
parent a1dcb057
Hide whitespace changes
Inline Side-by-side
Showing with 3 additions and 0 deletions
doc/libav-merge.txt
View file @ 774295a3
...@@ -98,6 +98,9 @@ Stuff that didn't reach the codebase: ...@@ -98,6 +98,9 @@ Stuff that didn't reach the codebase:
- Removal of the custom atomic API (5cc0057f49, see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-March/209003.html) - Removal of the custom atomic API (5cc0057f49, see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-March/209003.html)
- new bitstream reader (see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209609.html) - new bitstream reader (see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209609.html)
- use of the bsf instead of our parser for vp9 superframes (see fa1749dd34) - use of the bsf instead of our parser for vp9 superframes (see fa1749dd34)
- use av_cpu_max_align() instead of hardcoding alignment requirements (see https://ffmpeg.org/pipermail/ffmpeg-devel/2017-September/215834.html)
- f44ec22e0 lavc: use av_cpu_max_align() instead of hardcoding alignment requirements
- 4de220d2e frame: allow align=0 (meaning automatic) for av_frame_get_buffer()
Collateral damage that needs work locally: Collateral damage that needs work locally:
------------------------------------------ ------------------------------------------
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment