From 774295a3e01a52e20df5b34b56d54f5ff4f0746a Mon Sep 17 00:00:00 2001 From: James Almer Date: Wed, 27 Sep 2017 23:57:30 -0300 Subject: [PATCH] doc/libav-merge: mention skipped or incomplete runtime alignment commits Signed-off-by: James Almer --- doc/libav-merge.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/libav-merge.txt b/doc/libav-merge.txt index 96b008b71b..4a46bfcf46 100644 --- a/doc/libav-merge.txt +++ b/doc/libav-merge.txt @@ -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) - 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 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: ------------------------------------------