From: "Ludovic Courtès" <ludo@gnu.org>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel <guix-devel@gnu.org>, Guile Devel <guile-devel@gnu.org>
Subject: Re: The size of ‘.go’ files
Date: Tue, 09 Jun 2020 18:09:50 +0200 [thread overview]
Message-ID: <87sgf4gr01.fsf@gnu.org> (raw)
In-Reply-To: <877dwirndv.fsf@igalia.com> (Andy Wingo's message of "Mon, 08 Jun 2020 10:07:56 +0200")
Hello!
Andy Wingo <wingo@igalia.com> skribis:
> A few points of information :)
Much appreciated!
> The guile.arities section starts with a sorted array of fixed-size
> headers, then is followed by a sequence of ULEB128 references to local
> variable names, including non-arguments. The size is a bit perplexing,
> I agree. I can think of a number of ways to encode that section
> differently but we'd need to understand a bit more about it and why the
> baseline compiler is significantly different.
‘.guile.arities’ size should be proportional to the number of
procedures, right? Additionally, if there are only/mostly thunks, the
string table for argument names should be small if not empty. For N
thunks, I would expect roughly N 28-byte headers + NxM UL128, say 100
bytes per thunk; there’s 1000 of them, so we should be ~100,000 bytes.
This is roughly what we get observe with the baseline compiler.
>> “.rtl-text” is 38% smaller and “.guile.arities” is almost a tenth of
>> what it was.
>
> The difference in the text are the new baseline intrinsics,
> e.g. $vector-ref. It goes in the opposite direction from instruction
> explosion, which sought to (1) make the JIT compiler easier by
> decomposing compound operations into their atomic parts, (2) make the
> optimizer learn more information from flow rather than type-checking
> side effects, and (3) allow the optimizer to eliminate / hoist / move
> the component pieces of macro-operations.
>
> However in the baseline compiler (2) and (3) aren't possible because
> there is no optimizer on that level, and therefore the result is
> actually a lose -- 10 micro-ops cost more than 1 macro-op because of
> stack traffic overhead, which isn't currently mitigated by the JIT (1).
>
> So instruction explosion is residual code explosion, which should pay
> off in theory, but not for the baseline compiler. So I added new
> intrinsics for e.g. $vector-ref et al. Thus the smaller code size.
Yes, that makes a lot of sense. In particular, this file must use the
struct intrinsics a lot.
> There are more possibilities for making code size smaller, e.g. having
> two equivalent encodings for bytecode, where one is smaller:
>
> https://webkit.org/blog/9329/a-new-bytecode-format-for-javascriptcore/
Like THUMB, but for bytecode. :-)
I guess we could first analyze the generated code more closely and see
if there are opportunities there.
Thanks for the explanations!
Ludo’.
next prev parent reply other threads:[~2020-06-09 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 20:50 The size of ‘.go’ files Ludovic Courtès
2020-06-06 8:20 ` Mathieu Othacehe
2020-06-06 19:21 ` Katherine Cox-Buday
2020-06-07 9:07 ` Pierre Neidhardt
2020-06-08 8:07 ` Andy Wingo
2020-06-09 16:09 ` Ludovic Courtès [this message]
2020-06-24 12:11 ` Andy Wingo
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=87sgf4gr01.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.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.
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).