From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: Very slow check/nativecomp build
Date: Sun, 20 Feb 2022 20:10:56 +0200 [thread overview]
Message-ID: <838ru5wgr3.fsf@gnu.org> (raw)
In-Reply-To: <87ilt9o1pp.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 20 Feb 2022 19:02:58 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 20 Feb 2022 19:02:58 +0100
> Cc: emacs-devel@gnu.org
>
> Alan Mackenzie <acm@muc.de> writes:
>
> > With the --enable-checking option? Are you sure you're not remembering
> > it with just --with-native-compilation? --enable-checking makes things
> > _much_ slower.
>
> Yes, I must be misremembering. nativecomp without checking still takes
> about five minutes, and I checked with a nativecomp build from a couple
> months back -- it also takes about 14 minutes with nativecomp +
> checking.
As Stefan points out, this shouldn't happen. So we should try and
find the reason for such slowdown from using --enable-checking.
next prev parent reply other threads:[~2022-02-20 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 16:46 Very slow check/nativecomp build Lars Ingebrigtsen
2022-02-20 17:10 ` Alan Mackenzie
2022-02-20 17:35 ` Stefan Monnier
2022-02-20 18:02 ` Lars Ingebrigtsen
2022-02-20 18:10 ` Eli Zaretskii [this message]
2022-02-20 18:35 ` 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
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=838ru5wgr3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@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).