From: "T.V Raman" <raman@google.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: origin/features/native-comp: Where do jitted .eln files go?
Date: Sun, 30 Aug 2020 07:07:36 -0700 [thread overview]
Message-ID: <p91r1ro1b2v.fsf@google.com> (raw)
In-Reply-To: <xjf8sdwzjov.fsf@sdf.org> (Andrea Corallo's message of "Sun, 30 Aug 2020 07:17:36 +0000")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 944 bytes --]
Andrea Corallo <akrl@sdf.org> writes:
Thanks!
In the meantime:
I rebuilt the native-branch, blew away my .emacs.d/eln-cache, eliminated
the error from dired-x (got rid of with-eval-after-load for that use
case) and now 99% of emacspeak appears to work reliably in native-emacs
--- still hunting down corner cases where it might be
failing. Incidentally I got a segfault when I hit tab in the minibuffer
while in vm (mail reader) haven't tracked it down yet > "T.V Raman" <raman@google.com> writes:
>
>> Hi Andrea,
>> Any plans to introduce a native equivalent of batch-byte-compile ---
>> might be useful in cases where load order matters e.g. with heavy use
>> of defadvice
>
> Hi Raman,
>
> We have `batch-native-compile', ATM this is producing only the .eln
> files so also batch-byte-compile must be invoked but it should do the
> job.
>
> Regards
>
> Andrea
--
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2020-08-30 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 19:52 origin/features/native-comp: Where do jitted .eln files go? T.V Raman
2020-08-25 6:18 ` Andrea Corallo via Emacs development discussions.
2020-08-25 15:23 ` Possible Race condition? " T.V Raman
2020-08-25 19:53 ` Andrea Corallo via Emacs development discussions.
2020-08-25 20:19 ` T.V Raman
2020-08-25 21:04 ` Andrea Corallo via Emacs development discussions.
[not found] ` <24394.59245.98750.79288@google.com>
[not found] ` <xjf8sdwzjov.fsf@sdf.org>
2020-08-30 14:07 ` T.V Raman [this message]
2020-08-30 20:33 ` Andrea Corallo via Emacs development discussions.
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=p91r1ro1b2v.fsf@google.com \
--to=raman@google.com \
--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 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.