all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Teika Kazura <teika@gmx.com>
To: 62317@debbugs.gnu.org
Cc: eliz@gnu.org, akrl@sdf.org
Subject: bug#62317: bug #62317: 28.2; This byte-compiled file behaves wrongly.
Date: Thu, 30 Mar 2023 18:20:45 +0900 (JST)	[thread overview]
Message-ID: <20230330.182045.1482877200410669261.teika@gmx.com> (raw)
In-Reply-To: <20230330.181859.275167795410318945.teika@gmx.com> <xjfa5zxgi6i.fsf@ma.sdf.org>

Hi. I found a relation of this bug to native compilation, but there's a new, independent bug. Anyway remember the problem here is the pair of require - set-buffer, and I'm using 28.2. (I know it's not safe. :p)

What surprises is that `native-compile-async' and `batch-native-compile' generate differnt codes. To show it, use the same init.el and a.el above. Byte-compile first a.el, then init.el. Next native-compile init.el. Run emacs, and the above bug appears.

The difference is that (i) if you use native-compile-async, by removing one of init-<hash>.eln or init.elc, the bug disappears, even if the other remains. But (ii) if you use "$ emacs -Q -batch -f batch-native-compile *el", eln in fact does not matter; only the presence of init.elc screws things up.

# Who can expect this?

At the very least, native-compilation has too many undocumented aspects. If you want, I'll open a new bug for this discrepancy.

# It's off-topic for this bug, but for the above sample code, automatic, asynchronous generation of an eln file does not happen, unlike the case of my real init.el. I can't find the reason yet.

Regards,
Teika






  parent reply	other threads:[~2023-03-30  9:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  3:54 bug#62317: 28.2; This byte-compiled file behaves wrongly Teika Kazura
2023-03-22  6:39 ` bug#62317: bug #62317: " Teika Kazura
2023-03-28  9:15 ` Teika Kazura
2023-03-28 12:08   ` Eli Zaretskii
2023-03-28 12:43     ` Andrea Corallo
2023-03-28 12:53       ` Eli Zaretskii
2023-03-28 13:49         ` Andrea Corallo
2023-03-30  9:20       ` Teika Kazura [this message]
2023-03-30  9:41         ` Eli Zaretskii
2023-04-01  7:36 ` Teika Kazura
2023-04-01  8:08   ` Eli Zaretskii
2023-04-01 16:27 ` bug#62317: " Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-01 17:10   ` Eli Zaretskii
2023-04-01 23:09     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-02  5:17       ` Eli Zaretskii
2023-09-12  0:08         ` Stefan Kangas
2023-09-12 18:12           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 14:02             ` Stefan Kangas
2023-09-13 14:45               ` Eli Zaretskii
2023-09-13 15:46                 ` Stefan Kangas
2023-04-01 23:15   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12  0:09     ` Stefan Kangas
2023-04-05  4:12   ` bug#62317: bug #62317: " Teika Kazura
     [not found] ` <handler.62317.C.169462003624017.notifdonectrl.0@debbugs.gnu.org>
2023-09-14  6:35   ` bug#62317: acknowledged by developer Teika Kazura

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=20230330.182045.1482877200410669261.teika@gmx.com \
    --to=teika@gmx.com \
    --cc=62317@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 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.