On 5/10/17 10:59 PM, Martin Storsjö wrote:
> This is more correct.
> ---
> libavformat/mpjpeg.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/libavformat/mpjpeg.c b/libavformat/mpjpeg.c
> index 1a78c32274..3b78cab225 100644
> --- a/libavformat/mpjpeg.c
> +++ b/l
This is more correct.
---
libavformat/mpjpeg.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/libavformat/mpjpeg.c b/libavformat/mpjpeg.c
index 1a78c32274..3b78cab225 100644
--- a/libavformat/mpjpeg.c
+++ b/libavformat/mpjpeg.c
@@ -26,7 +26,7 @@
static int mpjpeg_wr
On Tue, May 9, 2017 at 1:30 AM, wm4 wrote:
> On Mon, 8 May 2017 12:28:43 -0400
> Vittorio Giovara wrote:
>
>> This is currently an unsupported feature, only passthrough is allowed.
>>
>> Signed-off-by: Vittorio Giovara
>> ---
>> libavresample/utils.c | 8
>> 1 file changed, 8 insertio
On Tue, May 9, 2017 at 1:34 AM, wm4 wrote:
> On Mon, 8 May 2017 12:28:45 -0400
> Vittorio Giovara wrote:
>
>> Signed-off-by: Vittorio Giovara
>> ---
>> libavformat/avformat.h | 6 ++
>> libavformat/dump.c | 2 ++
>> 2 files changed, 8 insertions(+)
>>
>> diff --git a/libavformat/avform
On Wed, May 10, 2017 at 12:03 PM, Ricardo Constantino wrote:
> This is mostly a nitpick that's not caused by the patch but could be
> addressed
> while a new API is being made.
>
> Layouts "6.1" and "7.1(wide)" seem to be repeated in channel_layout_map. Is
> there
> any reason why (they're in some
This is mostly a nitpick that's not caused by the patch but could be
addressed
while a new API is being made.
Layouts "6.1" and "7.1(wide)" seem to be repeated in channel_layout_map. Is
there
any reason why (they're in some spec like that) or could they be changed to
something
like "6.1" and "6.1(
Clang support for Altivec/VSX uses a different approach.
---
Clang-4 sadly seeems to have some additional problems.
configure | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index d70e61593a..7f1b1b7b38 100755
--- a/configure
+++ b/configure
@@ -44
