From: npostavs@users.sourceforge.net
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 27416@debbugs.gnu.org
Subject: bug#27416: [PROPOSED] Simplify malloc replacement on glibc
Date: Sun, 18 Jun 2017 10:07:53 -0400 [thread overview]
Message-ID: <87shixqthi.fsf@users.sourceforge.net> (raw)
In-Reply-To: <20170618002818.20744-1-eggert@cs.ucla.edu> (Paul Eggert's message of "Sat, 17 Jun 2017 17:28:18 -0700")
tags 27416 + patch
severity 27416 wishlist
quit
Paul Eggert <eggert@cs.ucla.edu> writes:
> This avoids the need to build lib/e-gettime.o etc. on glibc
> platforms, as plain lib/gettime.o will do.
Could you add something like the summary you posted in
http://lists.gnu.org/archive/html/emacs-devel/2017-06/msg00351.html to
the commit message, I found the explanation here a bit confusing until I
read that.
[Replace] Emacs's hybrid malloc implementation on GNUish platforms
with a hybrid implementation that redefines malloc instead of
re-#defining it. That is, instead of defining a function
hybrid_malloc that can call either gmalloc or the system malloc (and
using the macro "#define malloc hybrid_malloc" in Emacs code), Emacs
defines a function malloc that can call either gmalloc or the system
malloc (via the latter’s alternate name ‘__libc_malloc’), without
using a macro.
[T]he Emacs build process no longer needs to compile library files
twice. For example, it can simply build lib/gettime.o from
lib/gettime.c, rather than having to build both lib/gettime.o and
lib/e-gettime.o. This is because there is only one malloc symbol
used by Emacs code, not two.
The hybrid malloc approach would not change on non-GNUish platforms.
next prev parent reply other threads:[~2017-06-18 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 0:28 bug#27416: [PROPOSED] Simplify malloc replacement on glibc Paul Eggert
2017-06-18 14:07 ` npostavs [this message]
2017-06-21 21:34 ` Paul Eggert
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=87shixqthi.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27416@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).