unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: guile-user@gnu.org
Subject: Re: GNU Guile 3.0.3 released
Date: Tue, 23 Jun 2020 17:52:47 +0200	[thread overview]
Message-ID: <87pn9pzsmo.fsf@gnu.org> (raw)
In-Reply-To: <87o8pam7e5.fsf@web.de> (Arne Babenhauserheide's message of "Tue,  23 Jun 2020 11:57:38 +0200")

Hi,

"Dr. Arne Babenhauserheide" <arne_bab@web.de> skribis:

>> "Dr. Arne Babenhauserheide" <arne_bab@web.de> skribis:
>>
>>> Are there already results about the difference in build-time from the git-repo?
>>
>> Andy wrote a nice post that includes performance comparisons:
>>
>>   https://wingolog.org/archives/2020/06/03/a-baseline-compiler-for-guile
>
> That post is why I ask. Would it be possible to get rid of the binaries
> in the tarballs with this change? Maybe by first compiling in O1 and
> recompiling after the basic modules are there?

The Guix package for Guile has always been built by first removing the
prebuilt/ directory.  It’s always been an option, it just takes more
time to build.  In 3.0.3, it takes a “reasonable” amount of time for
modern x86 machines (around 20mn with “make -j8” + tests).

Thanks,
Ludo’.



  reply	other threads:[~2020-06-23 15:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 21:04 GNU Guile 3.0.3 released Ludovic Courtès
2020-06-22 14:54 ` Jérémy Korwin-Zmijowski
2020-06-22 15:46 ` Dr. Arne Babenhauserheide
2020-06-23  7:39   ` Ludovic Courtès
2020-06-23  9:57     ` Dr. Arne Babenhauserheide
2020-06-23 15:52       ` Ludovic Courtès [this message]
2020-06-23 16:44         ` Dr. Arne Babenhauserheide
2020-06-22 20:50 ` Chris Vine
2020-06-23  8:05   ` Ludovic Courtès
2020-06-23  9:36     ` Chris Vine
2020-06-24 12:07       ` Andy Wingo
2020-06-24 13:15         ` Ludovic Courtès

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pn9pzsmo.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=arne_bab@web.de \
    --cc=guile-user@gnu.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. 
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).