From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!.POSTED!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: [Emacs-diffs] emacs-25 ee04aed: Fix handling of buffer relocation
	in regex.c functions
Date: Wed, 26 Oct 2016 05:29:34 +0300
Message-ID: <83shrjvo4x.fsf@gnu.org>
References: <20161023191028.10942.12099@vcs.savannah.gnu.org>
	<20161023191028.C103F220124@vcs.savannah.gnu.org>
	<jwvtwc2hkqm.fsf-monnier+emacsdiffs@gnu.org> <83mvhu5kn0.fsf@gnu.org>
	<jwvy41detqq.fsf-monnier+gmane.emacs.devel@gnu.org>
	<8360oh4tnt.fsf@gnu.org> <jwvy41dshfz.fsf-monnier+Inbox@gnu.org>
	<83oa2934yl.fsf@gnu.org> <jwvinsgd3np.fsf-monnier+Inbox@gnu.org>
	<83insgwg8j.fsf@gnu.org> <jwv7f8w8bt7.fsf-monnier+Inbox@gnu.org>
	<83vawgusi5.fsf@gnu.org>
	<jwvr3746vzp.fsf-monnier+gmane.emacs.devel@gnu.org>
Reply-To: Eli Zaretskii <eliz@gnu.org>
NNTP-Posting-Host: blaine.gmane.org
X-Trace: blaine.gmane.org 1477449081 15592 195.159.176.226 (26 Oct 2016 02:31:21 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Wed, 26 Oct 2016 02:31:21 +0000 (UTC)
Cc: emacs-devel@gnu.org
To: Stefan Monnier <monnier@iro.umontreal.ca>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 26 04:31:17 2016
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
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 <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1bzDzd-0001zG-9i
	for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2016 04:31:05 +0200
Original-Received: from localhost ([::1]:59227 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1bzDzf-00052T-KR
	for ged-emacs-devel@m.gmane.org; Tue, 25 Oct 2016 22:31:07 -0400
Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38323)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eliz@gnu.org>) id 1bzDyE-0004jd-OH
	for emacs-devel@gnu.org; Tue, 25 Oct 2016 22:29:39 -0400
Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eliz@gnu.org>) id 1bzDyA-0001k7-Q2
	for emacs-devel@gnu.org; Tue, 25 Oct 2016 22:29:38 -0400
Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:54747)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@gnu.org>)
	id 1bzDyA-0001k3-Ms; Tue, 25 Oct 2016 22:29:34 -0400
Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1827
	helo=home-c4e4a596f7)
	by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128)
	(Exim 4.82) (envelope-from <eliz@gnu.org>)
	id 1bzDyA-0001yL-2q; Tue, 25 Oct 2016 22:29:34 -0400
In-reply-to: <jwvr3746vzp.fsf-monnier+gmane.emacs.devel@gnu.org> (message from
	Stefan Monnier on Tue, 25 Oct 2016 15:59:41 -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." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-devel/>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Original-Sender: "Emacs-devel" <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Xref: news.gmane.org gmane.emacs.devel:208816
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/208816>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Tue, 25 Oct 2016 15:59:41 -0400
> 
> > I don't see the difference.  If it turns out that some platform's
> > native malloc or gmalloc causes memory fragmentation, we will have to
> > find a solution, perhaps mmap or something else.
> 
> I consider mmap to be a good answer.

If it's needed.  But we don't know yet if it is.