From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Is byte-compiled code supposed to call `make-byte-code'?
Date: Wed, 25 May 2016 10:53:36 +0200 [thread overview]
Message-ID: <CAG7BpapgJwoufDM89Ton9PcjfRTQOX09ERbCWGVdJss93r59MQ@mail.gmail.com> (raw)
In-Reply-To: <87iny3rw6r.fsf@linux-m68k.org>
Andreas Schwab wrote:
> But it isn't a constant, it depends on the function's argument.
You are right, didn't think about it. However, given that it is a
repetetive process, shouldn't all constant parts of it be moved to C
level instead of bytecode, as an optimization? E.g. add (make-closure
descriptor &rest constants), where descriptor would include the actual
bytecode, arglist, depth and constants inherited from outer closure?
Then `xxx' would disassemble to something like
0 constant mapcar
1 constant make-closure
2 constant <<descriptor>>
3 stack-ref <<fn>>
5 call 2
6 constant (1 2 3)
7 call 2
9 return
Thus, bytecode size would decrease for closure-heavy code and speed
likely improve as well.
Paul
next prev parent reply other threads:[~2016-05-25 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 20:58 Is byte-compiled code supposed to call `make-byte-code'? Paul Pogonyshev
2016-05-24 21:19 ` Andreas Schwab
2016-05-25 8:53 ` Paul Pogonyshev [this message]
2016-05-25 14:13 ` Stefan Monnier
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=CAG7BpapgJwoufDM89Ton9PcjfRTQOX09ERbCWGVdJss93r59MQ@mail.gmail.com \
--to=pogonyshev@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.
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).