From: Paul Eggert <eggert@cs.ucla.edu>
To: Daniel Colascione <dancol@dancol.org>
Cc: Tom Tromey <tom@tromey.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: pdumping "into" the executable
Date: Mon, 26 Feb 2018 15:17:06 -0800 [thread overview]
Message-ID: <41ac3ca1-a850-2c8a-0ad4-6b410b3932aa@cs.ucla.edu> (raw)
In-Reply-To: <05c667d7-ad68-925b-75e6-5834ee528aa6@dancol.org>
On 02/26/2018 02:22 PM, Daniel Colascione wrote:
> On 12/31/1969 04:00 PM, Paul Eggert wrote:
>> On 02/26/2018 01:18 PM, dancol@dancol.org wrote:
>>>> Or, just turn the dump to a C file, then compile it
>>>> and do a second link. Aside from (maybe hypothetical) C compiler
>>>> limits, that would be very portable.
>>> But not redumpable.
>>
>> Why couldn't it be redumpable? All that the user should need is a C
>> compiler. That's not unreasonable.
>
> I thought we had this argument back when we were talking about
> modules. I think it's unacceptable to require a C compiler and the
> presence of Emacs unlinked objects for the proper operation of an
> end-user feature.
Although using a dumped Emacs is an end-user feature, dumping and
redumping are not. Dumping and/or redumping are techniques used to build
Emacs, and in practice they should be part of a software build system;
for such a thing it's reasonable to assume a C compiler.
We already assume a C compiler (or equivalent) when building modules; we
don't assume a C compiler only when people are using the modules.
Dumping is similar.
>
>>> Besides, the problem with a second link is that it might change the
>>> relative positions of symbols within Emac
>>
>> How could that be a problem? Symbols known to C code are known by
>> their fixed offsets and the second link wouldn't change these
>> offsets, and symbols not known to C code need to be reallocated
>> anyway during loading.
>
> The linker is what determines into-translation-unit offsets, not the
> compiler. The offsets are patched in at link time. There's no
> particular requirement to perform the link the same way every time.
For Lisp symbols visible to C, Emacs master currently determines symbol
offsets at C-compile-time, not at link time. Does pdumper change this?
If so, how and why does it change this? And if not, then I don't see the
problem.
next prev parent reply other threads:[~2018-02-26 23:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 13:38 pdumping "into" the executable Stefan Monnier
2018-02-26 17:00 ` Daniel Colascione
2018-02-26 21:10 ` Tom Tromey
2018-02-26 21:18 ` dancol
2018-02-26 22:07 ` Paul Eggert
2018-02-26 22:22 ` Daniel Colascione
2018-02-26 23:17 ` Paul Eggert [this message]
2018-02-26 23:34 ` dancol
2018-02-26 23:41 ` dancol
2018-02-27 0:09 ` Drew Adams
2018-02-27 0:16 ` dancol
2018-02-27 7:55 ` John Wiegley
2018-02-27 13:47 ` Dmitry Gutov
2018-02-27 14:47 ` Stefan Monnier
2018-02-27 18:32 ` John Wiegley
2018-02-26 22:34 ` Clément Pit-Claudel
2018-02-26 22:47 ` Daniel Colascione
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=41ac3ca1-a850-2c8a-0ad4-6b410b3932aa@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tom@tromey.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).