On 7/9/2016 4:56 PM, Michael Niedermayer wrote:
> On Sat, Jul 09, 2016 at 04:07:14PM -0300, James Almer wrote:
>> On 7/9/2016 3:28 PM, Ronald S. Bultje wrote:
>>> Hi,
>>>
>>> On Sat, Jul 9, 2016 at 1:38 PM, James Almer wrote:
[14:31:33]
https://github.com/mpc-hc/mpc-hc/commit/fe1b4ebd1a
On Sat, Jul 09, 2016 at 04:07:14PM -0300, James Almer wrote:
> On 7/9/2016 3:28 PM, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Sat, Jul 9, 2016 at 1:38 PM, James Almer wrote:
> >> [14:31:33]
> >> https://github.com/mpc-hc/mpc-hc/commit/fe1b4ebd1ab69109c898fd4aa250013e18d2d116
> >> looks like som
On 7/9/2016 3:28 PM, Ronald S. Bultje wrote:
> Hi,
>
> On Sat, Jul 9, 2016 at 1:38 PM, James Almer wrote:
>> [14:31:33]
>> https://github.com/mpc-hc/mpc-hc/commit/fe1b4ebd1ab69109c898fd4aa250013e18d2d116
>> looks like some projects using ffmpeg are disabling tree vectorization to
>> fix crashes
Hi,
On Sat, Jul 9, 2016 at 1:38 PM, James Almer wrote:
> On 5/8/2016 4:00 AM, Reimar Döffinger wrote:
> > On 07.05.2016, at 02:56, Hendrik Leppkes wrote:
> >
> >> On Sat, May 7, 2016 at 2:02 AM, James Almer wrote:
> >>> On 5/6/2016 8:48 PM, Timothy Gu wrote:
> On Fri, May 06, 2016 at 12:0
On 5/8/2016 4:00 AM, Reimar Döffinger wrote:
> On 07.05.2016, at 02:56, Hendrik Leppkes wrote:
>
>> On Sat, May 7, 2016 at 2:02 AM, James Almer wrote:
>>> On 5/6/2016 8:48 PM, Timothy Gu wrote:
On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
>
> Just to document it,
On Sun, May 08, 2016 at 11:15:22PM -0300, James Almer wrote:
[...]
> >>> there where failures with some gcc versions recetly on fate that
> >>> disappesred when the gcc version used on these clients changed.
> >>> I dont know if anyone identified what was the cause of these issues
> >>
> >> Do you
On 5/8/2016 10:46 PM, Michael Niedermayer wrote:
> On Sun, May 08, 2016 at 10:40:10PM -0300, James Almer wrote:
>> On 5/8/2016 9:58 PM, Michael Niedermayer wrote:
>>> On Sun, May 08, 2016 at 02:55:13PM -0300, James Almer wrote:
On 5/8/2016 10:44 AM, Ronald S. Bultje wrote:
> Hi,
>
On Sun, May 08, 2016 at 10:40:10PM -0300, James Almer wrote:
> On 5/8/2016 9:58 PM, Michael Niedermayer wrote:
> > On Sun, May 08, 2016 at 02:55:13PM -0300, James Almer wrote:
> >> On 5/8/2016 10:44 AM, Ronald S. Bultje wrote:
> >>> Hi,
> >>>
> >>> On Fri, May 6, 2016 at 8:02 PM, James Almer wrote
On 5/8/2016 9:58 PM, Michael Niedermayer wrote:
> On Sun, May 08, 2016 at 02:55:13PM -0300, James Almer wrote:
>> On 5/8/2016 10:44 AM, Ronald S. Bultje wrote:
>>> Hi,
>>>
>>> On Fri, May 6, 2016 at 8:02 PM, James Almer wrote:
>>>
On 5/6/2016 8:48 PM, Timothy Gu wrote:
> On Fri, May 06, 2
On Sun, May 08, 2016 at 02:55:13PM -0300, James Almer wrote:
> On 5/8/2016 10:44 AM, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Fri, May 6, 2016 at 8:02 PM, James Almer wrote:
> >
> >> On 5/6/2016 8:48 PM, Timothy Gu wrote:
> >>> On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
>
On 5/8/16, Ronald S. Bultje wrote:
> Hi,
>
> On Sun, May 8, 2016 at 1:55 PM, James Almer wrote:
>
>> On 5/8/2016 10:44 AM, Ronald S. Bultje wrote:
>> > Hi,
>> >
>> > On Fri, May 6, 2016 at 8:02 PM, James Almer wrote:
>> >
>> >> On 5/6/2016 8:48 PM, Timothy Gu wrote:
>> >>> On Fri, May 06, 2016 a
Hi,
On Sun, May 8, 2016 at 1:55 PM, James Almer wrote:
> On 5/8/2016 10:44 AM, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Fri, May 6, 2016 at 8:02 PM, James Almer wrote:
> >
> >> On 5/6/2016 8:48 PM, Timothy Gu wrote:
> >>> On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
>
On 5/8/2016 10:44 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Fri, May 6, 2016 at 8:02 PM, James Almer wrote:
>
>> On 5/6/2016 8:48 PM, Timothy Gu wrote:
>>> On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
Just to document it, this has caused build breakage in various
>>>
Hi,
On Fri, May 6, 2016 at 8:02 PM, James Almer wrote:
> On 5/6/2016 8:48 PM, Timothy Gu wrote:
> > On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
> >>
> >> Just to document it, this has caused build breakage in various
> >> scenarios, even in GCC 5.3 (6.1 not tested).
> >>
> >
On 07.05.2016, at 02:56, Hendrik Leppkes wrote:
> On Sat, May 7, 2016 at 2:02 AM, James Almer wrote:
>> On 5/6/2016 8:48 PM, Timothy Gu wrote:
>>> On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
Just to document it, this has caused build breakage in various
scena
On 5/6/2016 6:08 AM, Hendrik Leppkes wrote:
On Tue, Feb 9, 2016 at 1:28 AM, Timothy Gu wrote:
On Sun, Jan 31, 2016 at 3:38 PM Timothy Gu wrote:
On Sat, Jan 30, 2016 at 07:27:22PM +, Derek Buitenhuis wrote:
On 1/30/2016 7:15 PM, Timothy Gu wrote:
FATE passes here on a x86-64 machine wit
On 5/6/2016 9:56 PM, Hendrik Leppkes wrote:
> On Sat, May 7, 2016 at 2:02 AM, James Almer wrote:
>> On 5/6/2016 8:48 PM, Timothy Gu wrote:
>>> On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
Just to document it, this has caused build breakage in various
scenarios, e
On Sat, May 7, 2016 at 2:02 AM, James Almer wrote:
> On 5/6/2016 8:48 PM, Timothy Gu wrote:
>> On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
>>>
>>> Just to document it, this has caused build breakage in various
>>> scenarios, even in GCC 5.3 (6.1 not tested).
>>>
>>> The latest
On 5/6/2016 8:48 PM, Timothy Gu wrote:
> On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
>>
>> Just to document it, this has caused build breakage in various
>> scenarios, even in GCC 5.3 (6.1 not tested).
>>
>> The latest reported on IRC just today here:
>> libavcodec/sbrdsp.c: In
On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
>
> Just to document it, this has caused build breakage in various
> scenarios, even in GCC 5.3 (6.1 not tested).
>
> The latest reported on IRC just today here:
> libavcodec/sbrdsp.c: In function 'sbr_neg_odd_64_c':
> libavcodec/sbr
On 5/6/2016 7:08 AM, Hendrik Leppkes wrote:
> On Tue, Feb 9, 2016 at 1:28 AM, Timothy Gu wrote:
>> On Sun, Jan 31, 2016 at 3:38 PM Timothy Gu wrote:
>>>
>>> On Sat, Jan 30, 2016 at 07:27:22PM +, Derek Buitenhuis wrote:
On 1/30/2016 7:15 PM, Timothy Gu wrote:
> FATE passes here on a x
On Fri, May 06, 2016 at 12:08:14PM +0200, Hendrik Leppkes wrote:
> On Tue, Feb 9, 2016 at 1:28 AM, Timothy Gu wrote:
> > On Sun, Jan 31, 2016 at 3:38 PM Timothy Gu wrote:
> >>
> >> On Sat, Jan 30, 2016 at 07:27:22PM +, Derek Buitenhuis wrote:
> >> > On 1/30/2016 7:15 PM, Timothy Gu wrote:
> >
On Tue, Feb 9, 2016 at 1:28 AM, Timothy Gu wrote:
> On Sun, Jan 31, 2016 at 3:38 PM Timothy Gu wrote:
>>
>> On Sat, Jan 30, 2016 at 07:27:22PM +, Derek Buitenhuis wrote:
>> > On 1/30/2016 7:15 PM, Timothy Gu wrote:
>> > > FATE passes here on a x86-64 machine with both GCC 4.9.2 and 5.3.1.
>>
On Sun, Jan 31, 2016 at 3:38 PM Timothy Gu wrote:
On Sat, Jan 30, 2016 at 07:27:22PM +, Derek Buitenhuis wrote:
> On 1/30/2016 7:15 PM, Timothy Gu wrote:
> > FATE passes here on a x86-64 machine with both GCC 4.9.2 and 5.3.1.
>
> Perhaps this should be restricted to x86?
Fair enough.
Push
On Sat, Jan 30, 2016 at 07:27:22PM +, Derek Buitenhuis wrote:
> On 1/30/2016 7:15 PM, Timothy Gu wrote:
> > FATE passes here on a x86-64 machine with both GCC 4.9.2 and 5.3.1.
>
> Perhaps this should be restricted to x86?
Fair enough.
Timothy
>From b75076b5d735005a5a8b25d47c21c38cbaebb30b Mo
On 1/30/2016 7:15 PM, Timothy Gu wrote:
> FATE passes here on a x86-64 machine with both GCC 4.9.2 and 5.3.1.
Perhaps this should be restricted to x86?
- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmp
4.9 was released precisely nine years after the first GCC version with
autovectorizer (4.0) and six years after the first GCC version with
`-ftree-vectorize` default to enabled on `-O3` (4.3). We've given GCC
enough time to fix those bugs.
FATE passes here on a x86-64 machine with both GCC 4.9.2 a
27 matches
Mail list logo
