[FFmpeg-devel] lurking bugs in the mmx-related assembler code (?)

Ronald S. Bultje rsbultje at gmail.com
Sun Oct 2 01:25:29 EEST 2016


On Sat, Oct 1, 2016 at 4:12 PM, <u-h8zb at aetey.se> wrote:

> Hello Ronald,
> On Sat, Oct 01, 2016 at 03:11:38PM -0400, Ronald S. Bultje wrote:
> > I'm not sure we want to go down the rabbit hole of allowing any code to
> be
> > executed inside frame en/decoding routines. Historically, IIRC, we have
> > disallowed float in user callbacks like request_frame also.
> >
> > Why does musl malloc require float? This is a real question. I can't
> think
> > of any reason why you'd want this.
> Taking the question for what it is, I have already answered - because
> it make sence for the C library implementation and functioning.
> We are not talking about what you and me "would like inside a standard
> library" but whether we can rely on the specified interfaces. The
> malloc() interface was apparently misunderstood as a promise to never
> do float. There is no such promise.

Can malloc call sleep() then?


More information about the ffmpeg-devel mailing list