From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52138@debbugs.gnu.org, 51308@debbugs.gnu.org, akrl@sdf.org
Subject: bug#51308: bug#52138: 29.0.50; Some tests fail on emba when run with native compilation
Date: Sun, 13 Mar 2022 07:45:43 +0200 [thread overview]
Message-ID: <834k42mmm0.fsf@gnu.org> (raw)
In-Reply-To: <87pmmqyhyu.fsf_-_@gnus.org> (message from Lars Ingebrigtsen on Sat, 12 Mar 2022 22:32:57 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 12 Mar 2022 22:32:57 +0100
> Cc: 52138@debbugs.gnu.org, Andrea Corallo <akrl@sdf.org>
>
> > Returning the .elc file would fix this, but I don't know what other
> > repercussions there might be.
>
> I've now done this change (which fixes this test failure), and I don't
> see any other regressions, so I've pushed it to Emacs 29.
Did you check that loading a .elc file via load-library still triggers
async native-compilation when there's no .eln file or it is not
up-to-date with the .el file? And what about loading a .el or .elc
file with an explicit extension -- that should NOT trigger
native-compilation even if there's no up-to-date .eln file.
next prev parent reply other threads:[~2022-03-13 5:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 18:20 bug#51308: 29.0.50; A number of tests fail with AOT Lars Ingebrigtsen
2021-10-20 18:28 ` Eli Zaretskii
2021-10-21 3:04 ` Lars Ingebrigtsen
2021-10-21 4:20 ` Lars Ingebrigtsen
2022-03-12 21:32 ` bug#51308: bug#52138: 29.0.50; Some tests fail on emba when run with native compilation Lars Ingebrigtsen
2022-03-13 5:45 ` Eli Zaretskii [this message]
2022-03-13 14:14 ` Lars Ingebrigtsen
2022-03-13 16:40 ` bug#52138: " Eli Zaretskii
2021-10-21 4:31 ` bug#51308: 29.0.50; A number of tests fail with AOT Lars Ingebrigtsen
2022-03-12 21:42 ` bug#51308: bug#52138: 29.0.50; Some tests fail on emba when run with native compilation Lars Ingebrigtsen
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=834k42mmm0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51308@debbugs.gnu.org \
--cc=52138@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=larsi@gnus.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.