Le septidi 7 fructidor, an CCXXIV, Ronald S. Bultje a écrit :
> On Tue, Apr 21, 2015 at 9:43 AM, Nicolas George wrote:
> > Le duodi 2 floréal, an CCXXIII, wm4 a écrit :
> > > Isn't the problem that realloc() doesn't keep the alignment?
> > No. That problem exists too
>
>
> That seems counter-int
Hi,
On Tue, Apr 21, 2015 at 9:43 AM, Nicolas George wrote:
> Le duodi 2 floréal, an CCXXIII, wm4 a écrit :
> > Isn't the problem that realloc() doesn't keep the alignment?
>
> No. That problem exists too
That seems counter-intuitive. The problem does not exist, but it does exist
too?
If you'r
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 shou
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 h
Le duodi 2 floréal, an CCXXIII, Michael Niedermayer a écrit :
> the only case iam aware of was some memory debugger which crashed
> when realloc & malloc where mixed (thats clearly a bug in the debugger
> as it should never crash, warn / fail maybe but not crash)
I was referring to this one:
comm
On Tue, Apr 21, 2015 at 03:43:59PM +0200, Nicolas George wrote:
> Le duodi 2 floréal, an CCXXIII, wm4 a écrit :
> > Isn't the problem that realloc() doesn't keep the alignment?
>
> No. That problem exists too, but is irrelevant for the current code base:
> there has been one bug of that kind about
Le duodi 2 floréal, an CCXXIII, wm4 a écrit :
> Isn't the problem that realloc() doesn't keep the alignment?
No. That problem exists too, but is irrelevant for the current code base:
there has been one bug of that kind about three years ago, AFAIK that is
all.
The problem that was addressed here
On Tue, 21 Apr 2015 15:12:36 +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 s
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 see
