unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: akrl@sdf.org
Cc: 50934-done@debbugs.gnu.org
Subject: bug#50934: 28.0.60; paren.el should be preloaded
Date: Fri, 08 Oct 2021 14:26:47 +0300	[thread overview]
Message-ID: <83y273ycy0.fsf@gnu.org> (raw)
In-Reply-To: <83bl47deti.fsf@gnu.org> (message from Eli Zaretskii on Sat, 02 Oct 2021 11:13:45 +0300)

> Date: Sat, 02 Oct 2021 11:13:45 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 50934@debbugs.gnu.org
> 
> > From: Andrea Corallo <akrl@sdf.org>
> > Cc: 50934@debbugs.gnu.org
> > Date: Fri, 01 Oct 2021 13:35:57 +0000
> > 
> > > The native-compilation build is already painfully slow, and most of it
> > > isn't spent in COMPILE_FIRST.  We could, of course, add those files to
> > > shortlisp instead, if you think this is better.
> > 
> > I suspect shortlisp might be a better option (the number of threads of
> > the machine here comes into play as well), but I guess a measure is the
> > only way to get an answer.  IOW just wanted to raise the warning.
> 
> I tried to add these to shortlisp, after the value is exported as
> $LISP_PRELOADED, but that didn't work: the added files were only
> byte-compiled, not ELC+ELN-compiled.  I cannot figure out why this
> happens.  I think this mystery should be resolved, so we would know
> how to add files to AOT native compilation without adding them to
> COMPILE_FIRST and without putting them into preloaded/.  I also cannot
> figure out how come some files not mentioned in shortlisp end up being
> ELC+ELN-compiled (for example emoji-zwj.el), also something that's
> worth understanding.
> 
> For now, I just added those files to COMPILE_FIRST.

The problem is solved, so I'm marking the bug done.





      reply	other threads:[~2021-10-08 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 10:49 bug#50934: 28.0.60; paren.el should be preloaded Eli Zaretskii
2021-10-01 12:35 ` Lars Ingebrigtsen
2021-10-01 12:55 ` Eli Zaretskii
2021-10-01 12:57   ` Lars Ingebrigtsen
2021-10-01 13:11   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-01 13:17     ` Eli Zaretskii
2021-10-01 13:35       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-02  8:13         ` Eli Zaretskii
2021-10-08 11:26           ` Eli Zaretskii [this message]

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=83y273ycy0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50934-done@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 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).