unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: "Gong-Yi Liao 廖宮毅" <gongyi.liao@gmail.com>
Cc: Frank Haun <fh@fhaun.de>, emacs-devel@gnu.org
Subject: Re: native-comp branch on Raspberry Pi 4
Date: Thu, 16 Apr 2020 19:35:17 +0000	[thread overview]
Message-ID: <xjfzhbbp6kq.fsf@sdf.org> (raw)
In-Reply-To: <CALKwrMAaCfPa-FcVU122-axuPJBhLG9RuOom4A9JZHGwrEjefA@mail.gmail.com> ("Gong-Yi Liao 廖宮毅"'s message of "Thu, 16 Apr 2020 13:50:50 -0500")

Gong-Yi Liao 廖宮毅 <gongyi.liao@gmail.com> writes:

> Just curious... how long does it take to compile gcc & emacs native
> on your aarch64 machine?  I have never successfully get it done on a
> Rpi4b... 

Aarch64 can be quite satisfying for compiling depending on the machine.
On the one I used speed 2 compile time was about 100min (64 cores),
newer generations should be faster.

Anyway configuring libgccjit with "--enable-host-shared
--enable-languages=jit --disable-bootstrap --enable-checking=release"
makes compilation surprisingly cheap.

And regarding Emacs

make NATIVE_FAST_BOOT=1 BYTE_COMPILE_EXTRA_FLAGS='--eval "(setq comp-speed 0)"'

Is the recipe to start with on constrained HW.  On "normal" machines it
completes in ~10 min so should be sustainable on any system.

Andrea

-- 
akrl@sdf.org



      reply	other threads:[~2020-04-16 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 16:17 native-comp branch on Raspberry Pi 4 Frank Haun
2020-04-16 17:06 ` Gong-Yi Liao 廖宮毅
2020-04-16 17:18   ` Andrea Corallo
2020-04-16 18:50     ` Gong-Yi Liao 廖宮毅
2020-04-16 19:35       ` Andrea Corallo [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=xjfzhbbp6kq.fsf@sdf.org \
    --to=akrl@sdf.org \
    --cc=emacs-devel@gnu.org \
    --cc=fh@fhaun.de \
    --cc=gongyi.liao@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).