From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org
Cc: 24892@debbugs.gnu.org
Subject: bug#24892: {s, }brk removed from FreeBSD 11.x and later, arm64 architecture
Date: Wed, 9 Nov 2016 17:40:17 -0800 [thread overview]
Message-ID: <50fc10b5-f02d-a2eb-048d-1064bcffb62f@cs.ucla.edu> (raw)
In-Reply-To: <E1c4d8f-0005Jj-3Q@fencepost.gnu.org>
On 11/09/2016 04:22 PM, Richard Stallman wrote:
> The point of memory-limit was to enable features useful for users.
> If memory-limit doesn't work any more, those features don't either.
>
> What exactly were those features? What problems did they help
> users deal with?
I assume memory-limit was an attempt to let Lisp code diagnose when
memory was getting low in Emacs, circa 1992. The memory-limit function
was added in commit 20d2471455526acfd5fe96681ea31f0eac88fae4 by Jim
Blandy on 1992-10-03. As far as I can see the function was never
successful, in the sense that this part of the code was being developed
at the time and that Emacs eventually used other methods (e.g., calls
from C to sbrk (0)) to get the information that memory-limit was returning.
> Are they completely unnecessary now? If not, can we make them
> function again? Or provide other features to deal with the same
> problems?
This particular feature, whatever it was, seems to have become
unnecessary in late 1992, soon after it was added.
next prev parent reply other threads:[~2016-11-10 1:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 6:01 bug#24892: {s, }brk removed from FreeBSD 11.x and later, arm64 architecture Ashish SHUKLA
2016-11-07 15:19 ` Eli Zaretskii
2016-11-08 17:54 ` Paul Eggert
2016-11-08 20:11 ` Eli Zaretskii
2016-11-08 21:41 ` Paul Eggert
2016-11-09 3:34 ` Eli Zaretskii
2016-11-09 8:27 ` Paul Eggert
2016-11-09 15:49 ` Eli Zaretskii
2016-11-10 1:47 ` Paul Eggert
2016-11-10 16:13 ` Eli Zaretskii
2016-11-10 16:59 ` Paul Eggert
2016-11-10 17:24 ` Eli Zaretskii
2016-11-10 0:22 ` Richard Stallman
2016-11-10 1:40 ` Paul Eggert [this message]
2016-11-09 4:29 ` Ashish SHUKLA
2016-11-09 8:26 ` Paul Eggert
2016-11-09 9:46 ` Andreas Schwab
2016-11-09 15:50 ` Eli Zaretskii
2016-11-09 17:52 ` Paul Eggert
2016-11-10 9:52 ` Andreas Schwab
2016-11-10 16:23 ` Paul Eggert
2016-11-10 17:00 ` Andreas Schwab
2016-11-10 17:22 ` Paul Eggert
2016-11-10 17:33 ` Andreas Schwab
2016-11-11 2:48 ` Paul Eggert
2016-11-17 17:27 ` Eli Zaretskii
2016-11-18 12:29 ` Ashish SHUKLA
2016-11-18 16:21 ` Paul Eggert
2016-11-18 20:20 ` Ed Maste
2016-11-18 20:23 ` Brooks Davis
[not found] ` <CAPyFy2AL_OZWYpp+tiLSro_3WK1-H8Pdjy4-ZhUQChMQqageUw@mail.gmail.com>
2016-11-18 22:22 ` Paul Eggert
2016-11-19 6:57 ` Eli Zaretskii
2016-11-19 7:20 ` Eli Zaretskii
2017-09-02 13:37 ` Eli Zaretskii
2016-11-09 13:23 ` Ashish SHUKLA
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=50fc10b5-f02d-a2eb-048d-1064bcffb62f@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=24892@debbugs.gnu.org \
--cc=rms@gnu.org \
/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.