[FFmpeg-devel] [PATCH] avutil/mem: remove av_realloc / av_malloc incompatibility warning

Michael Niedermayer michael at niedermayer.cc
Tue Aug 23 14:25:41 EEST 2016

On Sun, Jan 10, 2016 at 04:29:47AM +0100, Michael Niedermayer wrote:
> On Tue, Apr 21, 2015 at 03:12:36PM +0200, Michael Niedermayer wrote:
> > memalign() is not guranteed to be compatible with free() or realloc()
> > and for platforms in this category we have --enable-memalign-hack
> > (which should be enabled automatically if such system is detected)
> > Trying to somehow half support systems that can free() memalign memory
> > but not reallocate it seems not worth the amount of work needed to
> > keep 2 then incompatible allocation systems and ensure their
> > seperation. That is unless this would affect a major platform
> > on which we want to avoid the memalign hack code
> > 
> > Signed-off-by: Michael Niedermayer <michaelni at gmx.at>
> > ---
> >  libavutil/mem.h |   24 ------------------------
> >  1 file changed, 24 deletions(-)
> is anyone against this patch ?
> people replace av_realloc by av_malloc, memcpy, av_free due to this
> text
> (example: [FFmpeg-devel] [PATCH v5] lavf/matroskadec: Normalize noncompliant A_QUICKTIME/V_QUICKTIME private data)


this warning is causing alot of problems, there just was another
developer that added complex code to seperate the allocations


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If a bugfix only changes things apparently unrelated to the bug with no
further explanation, that is a good sign that the bugfix is wrong.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20160823/7a6b8eb1/attachment.sig>

More information about the ffmpeg-devel mailing list