From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 47049@debbugs.gnu.org
Subject: bug#47049: [feature/native] macro-expansion cycle when compiling comp.el
Date: Fri, 12 Mar 2021 17:05:03 +0200 [thread overview]
Message-ID: <837dmcl8f4.fsf@gnu.org> (raw)
In-Reply-To: <xjflfavq9jd.fsf@sdf.org> (message from Andrea Corallo on Wed, 10 Mar 2021 16:05:10 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: 47049@debbugs.gnu.org
> Date: Wed, 10 Mar 2021 16:05:10 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 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.
Could this be somehow related to the crashes I see, which you cannot
reproduce? IOW, does this message mean comp.el is somehow incorrectly
compiled?
next prev parent reply other threads:[~2021-03-12 15: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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837dmcl8f4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47049@debbugs.gnu.org \
--cc=akrl@sdf.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.