GNU bug report logs -
#69480
Emacs Lisp needs, for its great 'native-compile', 'declare' and 'the' for fixnums and arrays.
Previous Next
Full log
View this message in rfc822 format
> From: Stephen Berman <stephen.berman <at> gmx.net>
> Cc: acorallo <at> gnu.org, robertstephenboyer <at> gmail.com, 69480 <at> debbugs.gnu.org
> Date: Fri, 01 Mar 2024 14:53:18 +0100
>
> On Fri, 01 Mar 2024 15:41:24 +0200 Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> >> That says almost all memory and CPU are consumed by `build-sieve':
> >
> > This is skewed, use cpu profiling instead of "memory" profiling.
>
> Ah, ok.
>
> >> But I don't see how that bears on the difference between native and byte
> >> compilation in my timings versus yours and Andrea's.
> >
> > My suggestion was to compare profiles in the byte-compiled and
> > native-compiled cases.
> >
> > Btw, are you running both cases in the same session? If so, don't:
> > restart Emacs and run the other case instead.
>
> Ok, I've now done that. Here's the report for the run with native
> compilation:
>
> 12599 95% - command-execute
> 12487 95% - funcall-interactively
> 12486 95% - eval-expression
> 12485 95% - #<compiled -0x5db3e1955cb81d1>
> 12485 95% - #<compiled -0x8a5cf032951a0fe>
> 12480 95% - eval
> 12480 95% - progn
> 12367 94% - benchmark-call
> 12367 94% - #<lambda 0x8c97b8cb7bd82>
> 12367 94% build-sieve
> 113 0% - emacs-lisp-native-compile-and-load
> 113 0% - emacs-lisp-native-compile
> 113 0% - native-compile
> 79 0% - comp--native-compile
> 37 0% - comp--fwprop
Why are subroutines of native-compilation in the profile?
This bug report was last modified 166 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.