[FFmpeg-devel] [PATCH] avfilter/showcqt: BASEFREQ and ENDFREQ cast to double
michaelni at gmx.at
Mon Nov 30 21:06:08 CET 2015
On Mon, Nov 30, 2015 at 07:02:47PM +0100, Nicolas George wrote:
> Le decadi 10 frimaire, an CCXXIV, Michael Niedermayer a écrit :
> > > ISO/IEC 9899:TC3
> > > 188.8.131.52.2 Characteristics of floating types <float.h>
> > >
> > > 8 Except for assignment and cast (which remove all extra range and precision), the values
> > > of operations with floating operands and values subject to the usual arithmetic
> > > conversions and of floating constants are evaluated to a format whose range and precision
> > > may be greater than required by the type. The use of evaluation formats is characterized
> > > by the implementation-defined value of FLT_EVAL_METHOD:19)
> > > -1 indeterminable;
> > > 0 evaluate all operations and constants just to the range and precision of the
> > > type;
> > > 1 evaluate operations and constants of type float and double to the
> > > range and precision of the double type, evaluate long double
> > > operations and constants to the range and precision of the long double
> > > type;
> > > 2 evaluate all operations and constants to the range and precision of the
> > > long double type.
> > > All other negative values for FLT_EVAL_METHOD characterize implementation-defined
> > > behavior.
> > a few more related parts:
> > 5 The accuracy of the floating-point operations (+, -, *, /) and of the library functions in
> > <math.h> and <complex.h> that return floating-point results is implementation-
> > defined, as is the accuracy of the conversion between floating-point internal
> > representations and string representations performed by the library functions in
> > <stdio.h>, <stdlib.h>, and <wchar.h>. The implementation may state that the
> > accuracy is unknown.
> > 184.108.40.206 Floating constants
> > 7 The translation-time conversion of floating constants should match the execution-time
> > conversion of character strings by library functions, such as strtod, given matching
> > inputs suitable for both conversions, the same result format, and default execution-time
> > rounding.64)
> I am not sure why you quoting this. Are you implying this is not a compiler
> bug, the compiler is actually allowed to do that? Possible. But still, I do
yes, i suspect that is not a compiler bug but i certainly do not have
deep enough knowledge of C to say that for sure
> not think we should apply this unless we actually understand what is going
> on here, why a cast that should not change anything does change the result.
> Otherwise, it could just be a coincidence, and break in a different way on a
> different compiler.
I would not be surprised if a strict and litteral reading of C would
allow that still to fail, but then theres the question if such
equals check is even possible in C in such a strict reading of the
and theres also IEEE ...
One could use a special value as default like -1 and check for that
which may be less likely to cause problems with float accuracy and
rounding in case the cast does not work on some real world case or
if the risk of it failing on some obscure plaform should be avoided
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: Digital signature
More information about the ffmpeg-devel