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 <michae...@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) [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is dangerous to be right in matters on which the established authorities are wrong. -- Voltaire
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
