From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: m43cap@yandex.com, herbert@mailbox.org, emacs-devel@gnu.org
Subject: Re: USE_LSB_TAG not supported on this platform
Date: Tue, 09 Feb 2016 18:59:09 +0200 [thread overview]
Message-ID: <83bn7pddlu.fsf@gnu.org> (raw)
In-Reply-To: <56B9A5B1.5080101@cs.ucla.edu> (message from Paul Eggert on Tue, 9 Feb 2016 00:39:13 -0800)
> Cc: herbert@mailbox.org, emacs-devel@gnu.org, m43cap@yandex.com
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 9 Feb 2016 00:39:13 -0800
>
> Eli Zaretskii wrote:
> > Could you please add a commentary explaining the need for this
> > additional layer of lmalloc/lrealloc?
>
> Sure. I gave it a shot in emacs-25 commit
> b1079c0f86c218f016a6c2e84ea402f4e175fc53 as part of a patch to improve
> portability to hosts where realloc and malloc can return pointers that are not
> multiples of 8. (I don't have access to any such hosts, which I think are rare
> nowadays though some may still exist.)
Thanks. Out of curiosity: which hosts can behave like that?
Also, why are we sure that the loops will end at some point on those
hosts? Shouldn't we perhaps set a limit to the loop iterations, to be
sure we don't infloop there?
next prev parent reply other threads:[~2016-02-09 16:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 8:32 USE_LSB_TAG not supported on this platform C. Baxter
2016-02-04 13:24 ` Stefan Monnier
2016-02-04 15:51 ` Paul Eggert
2016-02-04 22:29 ` Herbert J. Skuhra
2016-02-05 1:22 ` Paul Eggert
2016-02-05 9:45 ` Colin Baxter
2016-02-06 10:55 ` Herbert J. Skuhra
2016-02-06 16:04 ` Herbert J. Skuhra
2016-02-07 15:11 ` Wolfgang Jenkner
2016-02-07 19:14 ` Herbert J. Skuhra
2016-02-07 21:35 ` Herbert J. Skuhra
2016-02-08 19:45 ` Paul Eggert
2016-02-08 20:14 ` Eli Zaretskii
2016-02-09 8:39 ` Paul Eggert
2016-02-09 16:59 ` Eli Zaretskii [this message]
2016-02-09 17:37 ` Paul Eggert
2016-02-09 18:02 ` Eli Zaretskii
2016-02-10 19:29 ` Colin Baxter
2016-02-08 23:01 ` Herbert J. Skuhra
2016-02-09 1:10 ` Paul Eggert
2016-02-09 11:12 ` Herbert J. Skuhra
2016-02-09 23:37 ` Paul Eggert
2016-02-09 15:53 ` Wolfgang Jenkner
2016-02-09 23:33 ` Paul Eggert
2016-02-06 20:34 ` Paul Eggert
2016-02-07 16:52 ` Herbert J. Skuhra
2016-02-07 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=83bn7pddlu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=herbert@mailbox.org \
--cc=m43cap@yandex.com \
/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).