[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: When should ralloc.c be used?

From: Paul Eggert
Subject: Re: When should ralloc.c be used?
Date: Mon, 24 Oct 2016 09:21:50 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0

On 10/24/2016 12:44 AM, Eli Zaretskii wrote:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24358... Then there's bug#24764 ...

These bugs seem to be fixed now (thanks to you!). As Andreas pointed out, the problems with ralloc.c are not as severe as initially feared, since they should be limited to pointers to buffer text and should not extend to pointers to Lisp strings.

As I understand it, although the ralloc.c approach worked for a long time, it fell out of favor on common platforms and so hasn't been debugged as thoroughly for the past several years. Unfortunately, recent changes to glibc have caused ralloc.c to be used again on common GNU platforms and this are shaking out longstanding bugs with the ralloc.c approach. This means people using bleeding-edge glibc are suffering problems similar to what people on now-unusual platforms must have had for some time.

Surely we can fix these ralloc.c-related bugs as they come up. That being said, they are a hassle for users and maintainers, and if dropping ralloc.c works and doesn't cause significant performance degradation it sounds like that would be a win.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]