all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: fabrice.popineau@gmail.com, emacs-devel@gnu.org
Subject: Re: w32/w64 Emacs and gmalloc()
Date: Tue, 04 Mar 2014 05:49:04 +0200	[thread overview]
Message-ID: <83ha7esjwv.fsf@gnu.org> (raw)
In-Reply-To: <jwvsiqytzif.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: fabrice.popineau@gmail.com, emacs-devel@gnu.org
> Date: Mon, 03 Mar 2014 22:28:03 -0500
> 
> >> I'm just pointing out that it can be improved a bit by exposing the
> >> "freeable_p" test and use it in sweep_foo so we don't even try to
> >> free blocks when the free would be ignored.  Along the lines of the
> >> patch below.
> > Will this handle all the calls to xrealloc we have in the sources?
> 
> Not sure what you mean.  I think the answer is "no" because we're not
> trying to optimize all cases, only those that we (easily) can.

What I meant is this: if some cases of xrealloc still remain that will
try to reallocate a buffer allocated before dumping, then we still
need code to intercept the reallocation and make it call malloc
without freeing the frozen memory.



  reply	other threads:[~2014-03-04  3:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 16:39 w32/w64 Emacs and gmalloc() Fabrice Popineau
2014-02-28 17:21 ` Stefan Monnier
2014-03-01  7:02   ` Eli Zaretskii
2014-03-01 15:50     ` Stefan Monnier
2014-03-01 16:00       ` Fabrice Popineau
2014-03-01 18:08         ` Eli Zaretskii
2014-03-01 20:12           ` Fabrice Popineau
2014-03-01 20:29             ` Eli Zaretskii
2014-03-01 18:05       ` Eli Zaretskii
2014-03-04  3:28         ` Stefan Monnier
2014-03-04  3:49           ` Eli Zaretskii [this message]
2014-03-01  6:58 ` Eli Zaretskii
2014-03-01  9:57   ` Fabrice Popineau

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ha7esjwv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fabrice.popineau@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.