Is there a FAQ or other documentation on how to submit patches? There's a
compiler warning that's driving me nuts and I'd like to clean it up if I
can.
Thank you,
Mike
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listi
A later patch to configure to make sure it was defined, so the breakage
stopped. The patch for the configure option and the code should have been
atomic, IMNSHO.
On Thu, Jul 7, 2016 at 8:42 PM, Michael Niedermayer
wrote:
> On Thu, Jun 30, 2016 at 03:36:31PM +0200, Michael Niedermayer wrote:
> >
>From b2ddfdd9ed695a1f47ed6251369abca08864e3ab Mon Sep 17 00:00:00 2001
From: Mike Lieman
Date: Fri, 16 Aug 2024 23:05:51 -0400
Subject: [PATCH] use proper macro to avoid issue with prior
avutil/timestamp.c
patch causing long startup times with some files under mplayer
(ht
>
> FP_INFINITE is a return value from fpclassify(), not a double.
>
> Does maybe using av_int2double(UINT64_C(0xFFF) << 52) help your slow
> startup?
>
Sadly, no.
double log = (fpclassify(val) == FP_ZERO ? av_int2double(UINT64_C(0xFFF) <<
52) : floor(log10(fabs(val;
gives the same long-star
what's
going on in the for loops, but it seems something's going on in the for
loops, since it's not happening when I'm using the incorrect constant.
On Sat, Aug 17, 2024 at 10:07 AM Rémi Denis-Courmont
wrote:
>
>
> Le 17 août 2024 06:09:16
>
> On Sat, Aug 17, 2024 at 11:29 AM Hendrik Leppkes
> wrote:
> Or you could check if your build uses ffast-math, not sure we support that
>
Hot Dog! We have a weiner!
Removing -ffast-math from my mplayer build appears to have resolved the
issue. Thank you for your time and guidance.
