From: Brooks Davis <brooks@freebsd.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: freebsd-hackers@freebsd.org, 24892@debbugs.gnu.org,
Ashish SHUKLA <ashish.is@lostca.se>
Subject: bug#24892: {s, }brk removed from FreeBSD 11.x and later, arm64 architecture
Date: Fri, 18 Nov 2016 20:23:28 +0000 [thread overview]
Message-ID: <20161118202328.GA79070@spindle.one-eyed-alien.net> (raw)
In-Reply-To: <5ec481c4-41e1-c7dd-433d-f533653b132f@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]
On Fri, Nov 18, 2016 at 08:21:04AM -0800, Paul Eggert wrote:
> Ashish SHUKLA wrote:
>
> > One of the FreeBSD developer has
> > pointed me to this ongoing discussion[1] on freebsd-hackers@ list.
> >
> > References:
> > [1] https://lists.freebsd.org/pipermail/freebsd-hackers/2016-November/050144.html
>
> OK, thanks, I'll CC: freebsd-hackers. FreeBSD hackers: this is following up on
> this serious Emacs bug report, which says that Emacs no longer works on FreeBSD
> 11.x arm64:
>
> https://bugs.gnu.org/24892
>
> The referenced FreeBSD discussion appears to be under the misapprehension that
> sbrk is useful only to estimate how much memory is in use, and since this use
> has long been wrong sbrk should be unceremoniously removed. Unfortunately, this
> assumption is incorrect for Emacs, as (bleeding-edge) Emacs uses its own
> allocator during its build process, and reverts to malloc only during user
> operation. (The build-time Emacs makes a copy of itself in a new executable, and
> relies on sbrk during the build.) Obviously this is dicey and we are planning to
> change Emacs to make it more portable; however, this will require nontrivial
> reengineering on our part.
>
> In the meantime we respectfully request that sbrk functionality be kept in
> FreeBSD 11.x arm64 for a while. It is fine to mark it as deprecated or obsolete,
> or even rename it, but please do not remove the functionality entirely.
Under FreeBSD's stability rules if we shipped ANY release for a platforms
(e.g. arm64, riscv) with a system call, we must support it for the life
of the architecture (approximately FOREVER). As such, if any other
solution is viable, we'd prefer that.
What does emacs actually need from sbrk()? Could it get by with
something with the same interface allocating from .bss or does it need
its allocations to be at the end of .bss? I'm happy to put some time
into a userspace workaround if one is viable.
-- Brooks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-11-18 20:23 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
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 [this message]
[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=20161118202328.GA79070@spindle.one-eyed-alien.net \
--to=brooks@freebsd.org \
--cc=24892@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=eggert@cs.ucla.edu \
--cc=freebsd-hackers@freebsd.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.