From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs:Native-Comp Backtrace
Date: Wed, 26 Aug 2020 19:09:01 +0000 [thread overview]
Message-ID: <xjfr1rt1aya.fsf@sdf.org> (raw)
In-Reply-To: <p91v9h5cuq4.fsf@google.com> (T. V. Raman's message of "Wed, 26 Aug 2020 08:06:27 -0700")
"T.V Raman" <raman@google.com> writes:
> "T.V Raman" <raman@google.com> writes:
>
> Here is some more info based on a work-around:
>
> Conjecture: native-comp has issues with with-eval-after-load and
> friends:
>
> The following setup produced the afore-mentioned error:
>
> 1. In the emacs startup, load dired-x when dired is loaded:
> (with-eval-after-load "dired" (require 'dired-x))
> 2. dired-mode-hook contains dired-omit-mode defined in dired-x
> 3. During startup, a dired buffer is opened -- either via psession,
> desktop or some other means
>
> With the above, you get the error (symbol's function definition is
> void: dired-omit-mode)
>
> Fix: If in the startup file, you remove the with-eval-after-load and
> simply require dired-x, then it works.
>
> Additional info which lends credence to the conjecture:
>
> Emacspeak loads module-specific code using eval-after-load e.g. when
> "ido" is loaded, it loads emacspeak-ido after ido is done loading. In
> native-comp emacs, I find that (featurep 'emacspeak-ido) is nil after
> ido is loaded.
>
> I suspect use-package may also be affected in a similar way.
Hi Raman
thanks for having a look.
This issue sounds strange but before looking into it I'd like to rework
the advicing primitive mechanism for the native code.
This is a source of incompatibility that may cause a number of the small
strange behaviours we still see today. As a matter of fact today any
primitive that gets advised if is not listed in
`comp-never-optimize-functions' will misbehave with respect to the
vanilla implementation.
This should be the last non small area that need intervention and I'll
be on this very soon.
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-08-26 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 0:36 Emacs:Native-Comp Backtrace T.V Raman
2020-08-26 15:06 ` T.V Raman
2020-08-26 19:09 ` Andrea Corallo via Emacs development discussions. [this message]
2020-08-26 19:32 ` T.V Raman
2020-08-26 19:46 ` 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
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=xjfr1rt1aya.fsf@sdf.org \
--to=emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=raman@google.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).