From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 ee04aed: Fix handling of buffer relocation in regex.c functions
Date: Tue, 25 Oct 2016 22:40:34 +0300 [thread overview]
Message-ID: <83vawgusi5.fsf@gnu.org> (raw)
In-Reply-To: <jwv7f8w8bt7.fsf-monnier+Inbox@gnu.org> (message from Stefan Monnier on Tue, 25 Oct 2016 15:32:47 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Tue, 25 Oct 2016 15:32:47 -0400
>
> >> I think we can get out right away.
> [...]
> > I agree that there's a good chance we'll achieve this goal soon
> > enough, but we are not there yet. We just made the first step today
> > in that direction. I'm not even sure we will be able to achieve this
> > goal before Emacs 25.2 is released.
>
> Indeed, I meant "right away for master", not "right away for emacs-25".
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. And at least
theoretically some platform could remain with ralloc.c for the
observable future. We don't want to break people who track master.
next prev parent reply other threads:[~2016-10-25 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161023191028.10942.12099@vcs.savannah.gnu.org>
[not found] ` <20161023191028.C103F220124@vcs.savannah.gnu.org>
2016-10-23 20:31 ` [Emacs-diffs] emacs-25 ee04aed: Fix handling of buffer relocation in regex.c functions Stefan Monnier
2016-10-24 6:25 ` Eli Zaretskii
2016-10-24 13:56 ` Stefan Monnier
2016-10-24 16:07 ` Eli Zaretskii
2016-10-24 19:01 ` Stefan Monnier
2016-10-24 19:46 ` Eli Zaretskii
2016-10-25 12:20 ` Stefan Monnier
2016-10-25 16:22 ` Eli Zaretskii
2016-10-25 19:32 ` Stefan Monnier
2016-10-25 19:40 ` Eli Zaretskii [this message]
2016-10-25 19:59 ` Stefan Monnier
2016-10-26 2:29 ` Eli Zaretskii
2016-10-24 14:18 ` Stefan Monnier
2016-10-24 15:35 ` Eli Zaretskii
2016-11-04 8:37 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83vawgusi5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).