unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: robertstephenboyer@gmail.com, 69480@debbugs.gnu.org, acorallo@gnu.org
Subject: bug#69480: Emacs Lisp needs, for its great 'native-compile', 'declare' and 'the' for fixnums and arrays.
Date: Fri, 01 Mar 2024 14:45:39 +0200	[thread overview]
Message-ID: <86msriqfws.fsf@gnu.org> (raw)
In-Reply-To: <877cimuo5n.fsf@gmx.net> (message from Stephen Berman on Fri, 01 Mar 2024 13:33:56 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of
>  text editors" <bug-gnu-emacs@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,
>   Robert Boyer <robertstephenboyer@gmail.com>,  69480@debbugs.gnu.org
> Date: Fri, 01 Mar 2024 13:33:56 +0100
> 
> On Fri, 01 Mar 2024 07:18:29 -0500 Andrea Corallo <acorallo@gnu.org> wrote:
> 
> >> Why is the timing with native compilation so much slower than with byte
> >> compilation?
> >
> > Because the file is not lexically scoped so we are not running
> > optimizations.
> 
> Ah, ok.
> 
> > On my laptop I see:
> >
> > 11 secs byte compiled
> > 18 secs native compiled
> >
> > 7 secs byte compiled with lexical scope
> > 5 secs  native compiled with lexical scope.
> 
> I got these timings with lexical scope:
> 
> native compiled: (12.717023709000001 1 0.34653286699999997)
>   byte compiled: (9.597325325 1 0.38987931)
> 
> It's still slower with native compilation than with byte compilation on
> my machine, unlike on yours.  Do you have any idea why?

Maybe your system takes time to allocate memory?  This program
allocates almost 850MB of memory on my system, so maybe yours starts
paging?

Anyway, profiling could give some hints.





  reply	other threads:[~2024-03-01 12:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 19:40 bug#69480: Emacs Lisp needs, for its great 'native-compile', 'declare' and 'the' for fixnums and arrays Robert Boyer
2024-02-29 20:10 ` Eli Zaretskii
2024-02-29 20:54   ` Robert Boyer
2024-02-29 22:10     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01  6:45     ` Eli Zaretskii
2024-02-29 21:04   ` Robert Boyer
2024-03-01 11:28   ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:18     ` Andrea Corallo
2024-03-01 12:33       ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:45         ` Eli Zaretskii [this message]
2024-03-01 13:07           ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 13:41             ` Eli Zaretskii
2024-03-01 13:53               ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 14:07                 ` Andrea Corallo
2024-03-01 14:35                   ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 16:10                     ` Andrea Corallo
2024-03-01 19:36                       ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 16:34                 ` Eli Zaretskii
2024-03-01 19:36                   ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:40       ` Eli Zaretskii
2024-03-01 12:34     ` Eli Zaretskii

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=86msriqfws.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69480@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=robertstephenboyer@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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).