From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Bootstrap optimization
Date: Sun, 28 Oct 2018 08:24:20 +0100 [thread overview]
Message-ID: <CAA2XvwLMC_Ou8=7pxuYvoA9H5rotkG5uc0+P8XVC0TDdJkWpOQ@mail.gmail.com> (raw)
In-Reply-To: <87y3aiam5q.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Den sön 28 okt. 2018 02:35Mark H Weaver <mhw@netris.org> skrev:
> The downside of this approach to serialization is that when we add file
> X.scm to the list of objects to build serially, we force a full rebuild
> whenever X.scm is modified. At present, eval.scm is the only file that
> forces a full rebuild. Your patch would add psyntax-pp.scm to that
> list.
>
> I don't feel strongly about it, and maybe your patch is still a net
> benefit, but I very much wish we had a better way to optimize the early
> bootstrap without adding these bogus dependencies.
>
> > To which branch should this be applied, stable-2.2 or master?
>
> If we decide to adopt this approach, it should probably be committed to
> stable-2.2, but first I'd like to give other people an opportunity to
> share their thoughts on this.
>
> Thoughts?
Thank you for spotting this, Mark. I didn't think of this.
There seems to be a simple solution in using order-only prerequisites. I'll
test this later and suggest a new patch.
Best regards,
Mikael
[-- Attachment #2: Type: text/html, Size: 1534 bytes --]
next prev parent reply other threads:[~2018-10-28 7:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 12:25 Bootstrap optimization Mikael Djurfeldt
2018-10-28 1:34 ` Mark H Weaver
2018-10-28 7:24 ` Mikael Djurfeldt [this message]
2018-10-28 12:40 ` Mikael Djurfeldt
2018-10-28 22:33 ` Officially require GNU Make to build Guile? (was Re: Bootstrap optimization) Mark H Weaver
2018-10-29 0:12 ` Greg Troxel
2018-10-29 10:33 ` Mikael Djurfeldt
2018-10-30 6:04 ` Mark H Weaver
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='CAA2XvwLMC_Ou8=7pxuYvoA9H5rotkG5uc0+P8XVC0TDdJkWpOQ@mail.gmail.com' \
--to=mikael@djurfeldt.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).