From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: arash@gnu.org, 53497@debbugs.gnu.org, larsi@gnus.org
Subject: bug#53497: 29.0.50; native-compile after restarting Emacs
Date: Thu, 27 Jan 2022 12:58:37 +0000 [thread overview]
Message-ID: <xjfa6fhz66a.fsf@ma.sdf.org> (raw)
In-Reply-To: <83wnile8yp.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Jan 2022 13:03:58 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: arash@gnu.org, larsi@gnus.org, 53497@debbugs.gnu.org
>> Date: Thu, 27 Jan 2022 10:57:19 +0000
>>
>> I pushed d0aac84b2a as it seems to work for me here.
>
> Thanks. But is it right to set comp--loadable regardless of whether
> native-comp-available-p returns non-nil?
In principle I'd say so, otherwhise we'll keep accumulating filenames in
`comp--delayed-sources' for all the session.
If we don't want to have errors raised by the deferred compilation when
an Emacs with native comp support is running without the native compiler
available I think we should guard against `native-comp-available-p'
inside 'maybe_defer_native_compilation'. WDYT?
Thanks
Andrea
next prev parent reply other threads:[~2022-01-27 12:58 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 10:20 bug#53497: 29.0.50; native-compile after restarting Emacs Arash Esbati
2022-01-24 10:30 ` Lars Ingebrigtsen
2022-01-24 10:35 ` Arash Esbati
2022-01-24 10:40 ` Lars Ingebrigtsen
2022-01-24 11:00 ` Arash Esbati
2022-01-24 12:28 ` Eli Zaretskii
2022-01-24 12:43 ` Arash Esbati
2022-01-24 12:36 ` Eli Zaretskii
2022-01-24 12:50 ` Arash Esbati
2022-01-24 12:56 ` Eli Zaretskii
2022-01-24 13:33 ` Arash Esbati
2022-01-24 13:45 ` Eli Zaretskii
2022-01-24 13:50 ` Eli Zaretskii
2022-01-24 14:27 ` Andrea Corallo
2022-01-24 14:31 ` Eli Zaretskii
2022-01-24 17:17 ` Arash Esbati
2022-01-24 19:08 ` Eli Zaretskii
2022-01-25 11:01 ` Arash Esbati
2022-01-25 12:36 ` Eli Zaretskii
2022-01-25 12:49 ` Arash Esbati
2022-01-25 13:31 ` Eli Zaretskii
2022-01-26 11:25 ` Arash Esbati
2022-01-26 13:22 ` Eli Zaretskii
2022-01-26 14:58 ` Arash Esbati
2022-01-26 15:13 ` Eli Zaretskii
2022-01-26 15:20 ` Arash Esbati
2022-01-26 16:54 ` Eli Zaretskii
2022-01-26 19:06 ` Arash Esbati
2022-01-26 19:30 ` Eli Zaretskii
2022-01-26 15:58 ` Andrea Corallo
2022-01-27 10:11 ` Andrea Corallo
2022-01-27 10:31 ` Eli Zaretskii
2022-01-27 10:57 ` Andrea Corallo
2022-01-27 11:03 ` Eli Zaretskii
2022-01-27 12:58 ` Andrea Corallo [this message]
2022-01-27 15:03 ` Arash Esbati
2022-01-27 15:22 ` Eli Zaretskii
2022-01-27 16:27 ` Arash Esbati
2022-01-27 16:37 ` Andrea Corallo
2022-01-27 16:57 ` Eli Zaretskii
2022-01-27 17:22 ` Andrea Corallo
2022-01-27 22:21 ` Andrea Corallo
2022-01-28 9:24 ` Arash Esbati
2022-01-28 12:15 ` Eli Zaretskii
2022-01-28 15:12 ` Andrea Corallo
2022-01-28 16:02 ` Andrea Corallo
2022-01-28 16:30 ` Lars Ingebrigtsen
2022-01-29 7:40 ` Andrea Corallo
2022-01-29 10:02 ` Eli Zaretskii
2022-01-29 11:49 ` Arash Esbati
2022-01-27 16:58 ` Arash Esbati
2022-01-27 17:03 ` Eli Zaretskii
2022-01-28 9:26 ` Arash Esbati
2022-01-24 16:33 ` Arash Esbati
2022-01-24 17:07 ` Eli Zaretskii
2022-01-24 18:47 ` Arash Esbati
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=xjfa6fhz66a.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=53497@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=eliz@gnu.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 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).