On Wed, 2016-06-22 at 20:33 -0300, James Almer wrote:
> On 6/22/2016 8:15 PM, Dan Parrot wrote:
> > On Thu, 2016-06-23 at 01:03 +0200, Michael Niedermayer wrote:
> >> On Tue, Jun 21, 2016 at 12:04:42AM -0500, Dan Parrot wrote:
> >>> On Tue, 2016-06-21 at 02:22 +0200, Michael Niedermayer wrote:
> >>
On 6/22/2016 8:15 PM, Dan Parrot wrote:
> On Thu, 2016-06-23 at 01:03 +0200, Michael Niedermayer wrote:
>> On Tue, Jun 21, 2016 at 12:04:42AM -0500, Dan Parrot wrote:
>>> On Tue, 2016-06-21 at 02:22 +0200, Michael Niedermayer wrote:
On Mon, Jun 20, 2016 at 06:38:18PM -0500, Dan Parrot wrote:
>
Dan Parrot mail.com> writes:
> > Did you already test the TIMER macros?
>
> No I did not test with the TIMER macros.
If you refuse to run the requested performance test, please at
least post your patch, maybe others find the necessary time.
Carl Eugen
On Thu, 2016-06-23 at 01:03 +0200, Michael Niedermayer wrote:
> On Tue, Jun 21, 2016 at 12:04:42AM -0500, Dan Parrot wrote:
> > On Tue, 2016-06-21 at 02:22 +0200, Michael Niedermayer wrote:
> > > On Mon, Jun 20, 2016 at 06:38:18PM -0500, Dan Parrot wrote:
> > > > On Tue, 2016-06-21 at 01:06 +0200,
On 6/22/2016 7:36 PM, Carl Eugen Hoyos wrote:
> Dan Parrot mail.com> writes:
>
> [...]
>
> Did you already test the TIMER macros?
>
> I don't know if they work on ppc64le but we won't know
> until you tested them.
>
> Thank you, Carl Eugen
If this patch works (FATE passes on ppc64) and is fa
On Tue, Jun 21, 2016 at 12:04:42AM -0500, Dan Parrot wrote:
> On Tue, 2016-06-21 at 02:22 +0200, Michael Niedermayer wrote:
> > On Mon, Jun 20, 2016 at 06:38:18PM -0500, Dan Parrot wrote:
> > > On Tue, 2016-06-21 at 01:06 +0200, Michael Niedermayer wrote:
> > > > On Mon, Jun 20, 2016 at 05:55:47PM
On Wed, 2016-06-22 at 22:36 +, Carl Eugen Hoyos wrote:
> Dan Parrot mail.com> writes:
>
> [...]
>
> Did you already test the TIMER macros?
No I did not test with the TIMER macros. I don't see what that has to do
with Trac ticket #5570.
> I don't know if they work on ppc64le but we won't kn
Dan Parrot mail.com> writes:
[...]
Did you already test the TIMER macros?
I don't know if they work on ppc64le but we won't know
until you tested them.
Thank you, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/ma
On Wed, 2016-06-22 at 21:02 +, Carl Eugen Hoyos wrote:
> Dan Parrot mail.com> writes:
>
> > Could I get a yes or no answer on whether the patch will be applied?
>
> Please comment on my email: time make fate can be used to show
> large performance changes (although it isn't optimal), I don'
Dan Parrot mail.com> writes:
> Could I get a yes or no answer on whether the patch will be applied?
Please comment on my email: time make fate can be used to show
large performance changes (although it isn't optimal), I don't
think it can show the difference between a division and a shift.
Ca
Could I get a yes or no answer on whether the patch will be applied?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Tue, 2016-06-21 at 00:04 -0500, Dan Parrot wrote:
> On Tue, 2016-06-21 at 02:22 +0200, Michael Niedermayer wrote:
> > On Mon, Jun 20, 2016 at 06:38:18PM -0500, Dan Parrot wrote:
> > > On Tue, 2016-06-21 at 01:06 +0200, Michael Niedermayer wrote:
> > > > On Mon, Jun 20, 2016 at 05:55:47PM -0500,
Dan Parrot mail.com> writes:
> "/usr/bin/time -p make -j 4 fate SAMPLES=fate-suite/"
I would expect that this depends on many factors outside
of your patch.
You could test with the START_TIMER and STOP_TIMER macros.
(Or look at the asm code that is produced...)
Carl Eugen
On Tue, 2016-06-21 at 02:22 +0200, Michael Niedermayer wrote:
> On Mon, Jun 20, 2016 at 06:38:18PM -0500, Dan Parrot wrote:
> > On Tue, 2016-06-21 at 01:06 +0200, Michael Niedermayer wrote:
> > > On Mon, Jun 20, 2016 at 05:55:47PM -0500, Dan Parrot wrote:
> > > > On Tue, 2016-06-21 at 00:45 +0200,
On Tue, 2016-06-21 at 02:22 +0200, Michael Niedermayer wrote:
> On Mon, Jun 20, 2016 at 06:38:18PM -0500, Dan Parrot wrote:
> > On Tue, 2016-06-21 at 01:06 +0200, Michael Niedermayer wrote:
> > > On Mon, Jun 20, 2016 at 05:55:47PM -0500, Dan Parrot wrote:
> > > > On Tue, 2016-06-21 at 00:45 +0200,
On Mon, Jun 20, 2016 at 06:38:18PM -0500, Dan Parrot wrote:
> On Tue, 2016-06-21 at 01:06 +0200, Michael Niedermayer wrote:
> > On Mon, Jun 20, 2016 at 05:55:47PM -0500, Dan Parrot wrote:
> > > On Tue, 2016-06-21 at 00:45 +0200, Michael Niedermayer wrote:
> > > > On Sun, Jun 19, 2016 at 09:57:42PM
On Tue, 2016-06-21 at 01:06 +0200, Michael Niedermayer wrote:
> On Mon, Jun 20, 2016 at 05:55:47PM -0500, Dan Parrot wrote:
> > On Tue, 2016-06-21 at 00:45 +0200, Michael Niedermayer wrote:
> > > On Sun, Jun 19, 2016 at 09:57:42PM +, Dan Parrot wrote:
> > > > First commit addressing Trac ticket
On Mon, Jun 20, 2016 at 05:55:47PM -0500, Dan Parrot wrote:
> On Tue, 2016-06-21 at 00:45 +0200, Michael Niedermayer wrote:
> > On Sun, Jun 19, 2016 at 09:57:42PM +, Dan Parrot wrote:
> > > First commit addressing Trac ticket #5570. Functions defined in
> > > libswscale/input.c
> > > have corr
On Tue, 2016-06-21 at 00:45 +0200, Michael Niedermayer wrote:
> On Sun, Jun 19, 2016 at 09:57:42PM +, Dan Parrot wrote:
> > First commit addressing Trac ticket #5570. Functions defined in
> > libswscale/input.c
> > have corresponding SIMD definitions in libswscale/ppc/input_vsx.c
> > ---
> >
On Sun, Jun 19, 2016 at 09:57:42PM +, Dan Parrot wrote:
> First commit addressing Trac ticket #5570. Functions defined in
> libswscale/input.c
> have corresponding SIMD definitions in libswscale/ppc/input_vsx.c
> ---
> libswscale/ppc/Makefile |1 +
> libswscale/ppc/input_vsx.c|
Could a PPC maintainer verify that this patch integrates cleanly into
the design? I would like to proceed with the remaining changes to close
out ticket #5570 but since the first patch was rejected, I am unsure on
whether I'll have to rewrite the code.
Thanks.
Dan.
On Sun, 2016-06-19 at 21:57 +00
First commit addressing Trac ticket #5570. Functions defined in
libswscale/input.c
have corresponding SIMD definitions in libswscale/ppc/input_vsx.c
---
libswscale/ppc/Makefile |1 +
libswscale/ppc/input_vsx.c| 1070 +
libswscale/swscale.c
On Wed, 2016-06-15 at 16:51 +0200, Hendrik Leppkes wrote:
> On Wed, Jun 15, 2016 at 6:25 AM, Dan Parrot wrote:
> > This is the first commit addressing Trac ticket #5570. Functions defined in
> > libswscale/input.c have corresponding definitions in
> > libswscale/ppc/input_vsx.h
> > The correspond
On Wed, 2016-06-15 at 11:19 +, Carl Eugen Hoyos wrote:
> Dan Parrot mail.com> writes:
>
> [...]
>
> I know this is isn't completely related but do you have time
> to look at ticket #5508?
> https://trac.ffmpeg.org/ticket/5508
> No active developer has hardware and knowledge to look into
>
On Wed, Jun 15, 2016 at 6:25 AM, Dan Parrot wrote:
> This is the first commit addressing Trac ticket #5570. Functions defined in
> libswscale/input.c have corresponding definitions in
> libswscale/ppc/input_vsx.h
> The corresponding function names in the latter contain the suffix "_vsx".
> ---
>
On Wed, 2016-06-15 at 10:15 +0200, Michael Niedermayer wrote:
> On Wed, Jun 15, 2016 at 04:25:11AM +, Dan Parrot wrote:
> > This is the first commit addressing Trac ticket #5570. Functions defined in
> > libswscale/input.c have corresponding definitions in
> > libswscale/ppc/input_vsx.h
> > Th
Dan Parrot mail.com> writes:
[...]
I know this is isn't completely related but do you have time
to look at ticket #5508?
https://trac.ffmpeg.org/ticket/5508
No active developer has hardware and knowledge to look into
this issue;-(
Carl Eugen
___
ff
On Wed, Jun 15, 2016 at 04:25:11AM +, Dan Parrot wrote:
> This is the first commit addressing Trac ticket #5570. Functions defined in
> libswscale/input.c have corresponding definitions in
> libswscale/ppc/input_vsx.h
> The corresponding function names in the latter contain the suffix "_vsx".
This is the first commit addressing Trac ticket #5570. Functions defined in
libswscale/input.c have corresponding definitions in libswscale/ppc/input_vsx.h
The corresponding function names in the latter contain the suffix "_vsx".
---
libswscale/input.c | 44 +--
libswscale/ppc/input_vsx.h
29 matches
Mail list logo
