From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: When should ralloc.c be used? Date: Sun, 23 Oct 2016 23:33:02 +0300 Message-ID: <83eg36n6v5.fsf@gnu.org> References: <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> <838ttfnmev.fsf@gnu.org> <837f8znk8f.fsf@gnu.org> <83zilvm2ud.fsf@gnu.org> <83r377m0i8.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1477254841 26428 195.159.176.226 (23 Oct 2016 20:34:01 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 23 Oct 2016 20:34:01 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 23 22:33:57 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 1byPSf-0004Yf-J2 for ged-emacs-devel@m.gmane.org; Sun, 23 Oct 2016 22:33:41 +0200 Original-Received: from localhost ([::1]:42348 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1byPSh-00042w-MF for ged-emacs-devel@m.gmane.org; Sun, 23 Oct 2016 16:33:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51166) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1byPS9-00042p-J1 for emacs-devel@gnu.org; Sun, 23 Oct 2016 16:33:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1byPS6-0004TR-HT for emacs-devel@gnu.org; Sun, 23 Oct 2016 16:33:09 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38668) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1byPS6-0004TL-ES; Sun, 23 Oct 2016 16:33:06 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3369 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1byPS5-0001A7-OQ; Sun, 23 Oct 2016 16:33:06 -0400 In-reply-to: (message from Stefan Monnier on Sun, 23 Oct 2016 16:23:38 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:208641 Archived-At: > From: Stefan Monnier > Date: Sun, 23 Oct 2016 16:23:38 -0400 > > >> It just means that I really see no reason why it wouldn't work just fine. > >> It's not like glibc's malloc was particularly magical, so we should be > >> able to do the same in gmalloc.c. > > AAIK, glibc's malloc doesn't use sbrk anymore. > > I don't think it matters very much since we use mmap for the buffers, No, we don't, not on GNU/Linux anyway. Or do you see USE_MMAP_FOR_BUFFERS defined to 1 in your src/config.h? > And if it proves to really be a problem, we could replace our gmalloc.c > with a more recent one which builds on mmap. That's a possibility, yes. But someone would have to bring such a gmalloc, and probably leave the current one as well, to minimize the impact on unaffected platforms.