unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 41077-done@debbugs.gnu.org
Subject: bug#41077: [feature/native-comp] virtual memory exhausted
Date: Sun, 10 May 2020 08:02:46 -0700	[thread overview]
Message-ID: <xjfftc7al49.fsf@sdf.org> (raw)
In-Reply-To: <877dxjn9wy.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sun, 10 May 2020 16:26:21 +0200")

Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:

> Hi Andrea!

Hi Kévin

> Thank you for implementing this blacklist; it turns out that
> char-fold.el was the only file my laptop could not handle[1], though as
> you'll see org.el was a strong contender.
>
> It took 3 days, but make -j1 successfully ran to completion on commit
> 92cf4bb.  In comparison, I've just compiled commit 9d8fc3a on master
> from scratch, and it took exactly 1 hour 35 minutes.

Wow thanks so much for the great report!  I'm glad it worked for you.

> As soon as I've figured out how to use the elisp-benchmarks package,
> I'll post some figures; is there a specific place (bug number,
> emacs-devel thread) where you usually collect such feedback?

Cool, we have no bug number for that.  I guess you can use the "On elisp
running native" thread or as you feel.

> Thank you for taking the time to guide me through compiling this branch.
> I know that reducing the memory footprint of native compilation is
> probably not your main focus right now, but I figured it would be
> interesting to provide some orders of magnitude.

It's very interesting thank you, your work will be usefull when we move
on the subject of compile-time/memory usage.  I've some idea on the code
generations side and we'll need to measure how it translates on the
compilation process.

Thanks

  Andrea

-- 
akrl@sdf.org





  reply	other threads:[~2020-05-10 15:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 15:08 bug#41077: [feature/native-comp] Segfaults when compiling ELC+ELN Kévin Le Gouguec
2020-05-04 16:31 ` Andrea Corallo
2020-05-04 20:57   ` Andrea Corallo
2020-05-04 21:05   ` Kévin Le Gouguec
2020-05-04 21:15     ` Andrea Corallo
2020-05-06 14:15       ` bug#41077: [feature/native-comp] virtual memory exhausted (was: bug#41077: [feature/native-comp] Segfaults when compiling ELC+ELN) Kévin Le Gouguec
     [not found]         ` <xjfftcd5chc.fsf@sdf.org>
2020-05-06 20:12           ` bug#41077: [feature/native-comp] virtual memory exhausted Andrea Corallo
2020-05-10 14:26             ` Kévin Le Gouguec
2020-05-10 15:02               ` Andrea Corallo [this message]
2020-05-10 22:04                 ` Kévin Le Gouguec
2020-05-10 22:17                   ` Andrea Corallo
2020-05-11  9:12                     ` Kévin Le Gouguec
2020-05-11 10:00                       ` Andrea Corallo

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=xjfftc7al49.fsf@sdf.org \
    --to=akrl@sdf.org \
    --cc=41077-done@debbugs.gnu.org \
    --cc=kevin.legouguec@gmail.com \
    /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).