From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: When should ralloc.c be used? Date: Mon, 24 Oct 2016 09:21:50 -0700 Organization: UCLA Computer Science Department Message-ID: <92ca0bf8-7ad4-a7de-70e5-ddbd6eab9741@cs.ucla.edu> References: <87k2djwumn.fsf@users.sourceforge.net> <83h98nidvd.fsf@gnu.org> <87eg3rvtsf.fsf@users.sourceforge.net> <83k2dihpm9.fsf@gnu.org> <8760p2wzgj.fsf@users.sourceforge.net> <838ttyhhzu.fsf@gnu.org> <871szqwu51.fsf@users.sourceforge.net> <831szqhbc2.fsf@gnu.org> <87d1itt79z.fsf_-_@users.sourceforge.net> <7baa18d4-2b09-caa8-005e-29008a383ad1@cs.ucla.edu> <83mvhwrgd5.fsf@gnu.org> <8539f38f-9a11-44c3-4de7-bb974c96206c@cs.ucla.edu> <8360ojpndr.fsf@gnu.org> <83wpgzo30m.fsf@gnu.org> <5a4bbe6d-08ce-e6c6-39d1-49c9cd6d1ffd@cs.ucla.edu> <83mvhvns9a.fsf@gnu.org> <83d1irnozo.fsf@gnu.org> <83mvhunb0d.fsf@gnu.org> <423fab24-9be6-778c-58c3-29a0b825b8c7@cs.ucla.edu> <83a8du5gy1.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1477327918 32468 195.159.176.226 (24 Oct 2016 16:51:58 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 24 Oct 2016 16:51:58 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 24 18:51:54 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1byiSw-000453-VL for ged-emacs-devel@m.gmane.org; Mon, 24 Oct 2016 18:51:15 +0200 Original-Received: from localhost ([::1]:48189 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1byiSz-0006cz-8X for ged-emacs-devel@m.gmane.org; Mon, 24 Oct 2016 12:51:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60010) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1byi0d-0006Gf-2W for emacs-devel@gnu.org; Mon, 24 Oct 2016 12:22:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1byi0c-00008s-8f for emacs-devel@gnu.org; Mon, 24 Oct 2016 12:21:59 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:57872) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1byi0Y-00007i-Et; Mon, 24 Oct 2016 12:21:54 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 7FB38161417; Mon, 24 Oct 2016 09:21:51 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id vcelllfqd23H; Mon, 24 Oct 2016 09:21:50 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id D85F516140B; Mon, 24 Oct 2016 09:21:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id LHQyrv_O0xOZ; Mon, 24 Oct 2016 09:21:50 -0700 (PDT) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id BFBAB1613CC; Mon, 24 Oct 2016 09:21:50 -0700 (PDT) In-Reply-To: <83a8du5gy1.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:208720 Archived-At: 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.