unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47049@debbugs.gnu.org
Subject: bug#47049: [feature/native] macro-expansion cycle when compiling comp.el
Date: Wed, 10 Mar 2021 16:05:10 +0000	[thread overview]
Message-ID: <xjflfavq9jd.fsf@sdf.org> (raw)
In-Reply-To: <83zgzbnm7i.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Mar 2021 15:59:45 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> From: eliz@HOME-C4E4A596F7.i-did-not-set--mail-host-address--so-tickle-me
> --text follows this line--
> I made some local modifications in comp.el, and used that modified
> comp.el for a while (by loading it manually at run time) to debug some
> problem.  Then I undid those local modifications of comp.el (by saying
> "git checkout") and said "make" to rebuild Emacs.  And I see this:
>
>     ELC      emacs-lisp/comp.elc
>   Warning: Eager macro-expansion skipped due to cycle:
>       => (load "comp.el") => (macroexpand-all (defalias 'comp-add-call-cstr  )) => (macroexpand (comp-loop-insn-in-block  )) => (load "comp.el")
>
> Why does this happen?

I'm not sure, but I can reproduce it.

I guess (just a guess) it might be because `comp-add-call-cstr' is using
a macro `comp-loop-insn-in-block' that is expanding with a
`cl-symbol-macrolet' inside? (no idea why this should be a problem).

> could it be that while comp.el was modified it
> got native-compiled, and now that inconsistent comp.eln gets in the
> way?

I think this has not to do specifically with native compilation.

I see it goes away removing '(setq load-prefer-newer t)' from the
invocation tho.

Perhaps somebody already more into the macro expansion business might
have some suggestion.

Thanks

  Andrea





  reply	other threads:[~2021-03-10 16:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 13:59 bug#47049: [feature/native] macro-expansion cycle when compiling comp.el Eli Zaretskii
2021-03-10 16:05 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-10 16:17   ` Eli Zaretskii
2021-03-11 15:26     ` Stefan Monnier
2021-03-12 20:02       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 20:55         ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 21:05         ` Stefan Monnier
2021-03-12 21:15           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 21:26             ` Stefan Monnier
2021-03-12 21:37               ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13  7:50                 ` Eli Zaretskii
2021-03-12 15:05   ` Eli Zaretskii
2021-03-12 15:30     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=xjflfavq9jd.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47049@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@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).