From: "Alex Bennée" <alex.bennee@linaro.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Where is the eln search path defined
Date: Sun, 17 May 2020 14:55:00 +0100 [thread overview]
Message-ID: <87eeri8y4r.fsf@linaro.org> (raw)
In-Reply-To: <xjfv9kuafxh.fsf@sdf.org>
Andrea Corallo <akrl@sdf.org> writes:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> Heh - so I patched pdumper to dump the variables at that point and
>> re-built:
>>
>> dump_do_dump_relocation: installation_state:2 ivoncation_dir:
>>
>> and now the built emacs boots up fine. So I'm guessing there
>> must have been a stale pdumper.o that didn't get built for some reason.
>>
>> Sorry for the noise.
>
> Hi Alex,
>
> no issue. Is very good somebody tests Aarch64, thanks for that!
While on that subject is there any sort of benchmarking used to see if a
given arch is generating good code? Certainly on x86 I noticed a
speed-up in gnus but that is more subjective than objective.
--
Alex Bennée
next prev parent reply other threads:[~2020-05-17 13:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 8:57 Where is the eln search path defined Alex Bennée
2020-05-15 16:49 ` Andrea Corallo
2020-05-15 17:19 ` Alex Bennée
2020-05-15 18:10 ` Andrea Corallo
2020-05-15 21:19 ` Alex Bennée
2020-05-15 21:55 ` Andrea Corallo
2020-05-17 11:00 ` Alex Bennée
2020-05-17 12:45 ` Andrea Corallo
2020-05-17 13:55 ` Alex Bennée [this message]
2020-05-17 14:26 ` Andrea Corallo
2020-05-18 15:10 ` Alex Bennée
2020-05-18 15:39 ` Andrea Corallo
2020-05-18 16:34 ` Alex Bennée
2020-05-18 17:23 ` Andrea Corallo
2020-05-19 10:39 ` Alex Bennée
2020-05-19 10:46 ` Andrea Corallo
2020-05-19 14:49 ` Andrea Corallo
2020-05-19 18:35 ` Alex Bennée
2020-05-19 18:57 ` Andrea Corallo
2020-05-20 7:06 ` Alex Bennée
2020-05-25 14:13 ` Alex Bennée
2020-05-25 15:01 ` Gong-Yi Liao 廖宮毅
2020-05-25 18:44 ` Andrea Corallo
2020-05-19 21:07 ` Thomas Fitzsimmons
2020-05-16 6:37 ` Eli Zaretskii
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=87eeri8y4r.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@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 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).