From: Paul Eggert <eggert@cs.ucla.edu>
To: Andreas Schwab <schwab@suse.de>
Cc: 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: Thu, 10 Nov 2016 08:23:40 -0800 [thread overview]
Message-ID: <40f8df50-b431-1ebd-221c-df2aa453aa81@cs.ucla.edu> (raw)
In-Reply-To: <mvmtwbfachr.fsf@hawking.suse.de>
On 11/10/2016 01:52 AM, Andreas Schwab wrote:
>> I'm curious about what the difference actually is,
> 17851608 bytes.
Thanks, and now I'm curious about where that difference comes from. I
assume that unexelf.c code like this:
#ifdef HAVE_SBRK
new_break = sbrk (0);
#else
new_break = (byte *) old_bss_addr + old_bss_size + 17851608;
#endif
would not be a good idea, even if it happens to work on this particular
ARM64 build, as the number 17851608 must be specific to the platform
and/or the build. (The number is 0 on x86-64, for example.) But how can
I compute the number?
Would it work if we copied the old sbrk.S from the ARM64 C library,
assemble and linked that, and then just call sbrk? (I don't have easy
access to this platform so I can't try tricks like this myself.)
next prev parent reply other threads:[~2016-11-10 16: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 [this message]
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=40f8df50-b431-1ebd-221c-df2aa453aa81@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=24892@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=schwab@suse.de \
/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.