From: Pip Cet <pipcet@gmail.com>
To: chuntaro <chuntaro@sakura-games.jp>
Cc: 34757@debbugs.gnu.org
Subject: bug#34757: Invalid bytecode from byte compiler
Date: Fri, 8 Mar 2019 21:13:37 +0000 [thread overview]
Message-ID: <CAOqdjBcTM6Z5KYLeFj=wiX2DvB57wGn1uZL96Gqr=fGtXNAQ=A@mail.gmail.com> (raw)
In-Reply-To: <ea07c24c-c0da-e7a3-d3d3-6680c664580f@sakura-games.jp>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
On Tue, Mar 5, 2019 at 3:30 PM chuntaro <chuntaro@sakura-games.jp> wrote:
>
> Invalid bytecode is output and error occurs when executed.
If I'm looking at this correctly, the problem is that the byte code
which is generated in an intermediate step:
0 constant 2
1 constant print
2 constant 1
3 call 1
4 discard
5 constant 3
6 return
is considered a "trivial function" by byte-compile-out-toplevel, which
assumes that all values on the stack are used by the call.
We could fix byte-compile-out-toplevel to properly analyze how many
stack arguments the call takes, but this patch simply treats forms
like this as nontrivial:
diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
index 0b8f8824b4c..4e54e08ce14 100644
--- a/lisp/emacs-lisp/bytecomp.el
+++ b/lisp/emacs-lisp/bytecomp.el
@@ -3025,6 +3025,7 @@ byte-compile-out-toplevel
(or (null (cdr rest))
(and (memq output-type '(file progn t))
(cdr (cdr rest))
+ (eql (length body) (cdr (car rest)))
(eq (car (nth 1 rest)) 'byte-discard)
(progn (setq rest (cdr rest)) t))))
(setq maycall nil) ; Only allow one real function call.
[-- Attachment #2: emacs-34757.diff --]
[-- Type: text/x-patch, Size: 674 bytes --]
diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
index 0b8f8824b4c..4e54e08ce14 100644
--- a/lisp/emacs-lisp/bytecomp.el
+++ b/lisp/emacs-lisp/bytecomp.el
@@ -3025,6 +3025,7 @@ byte-compile-out-toplevel
(or (null (cdr rest))
(and (memq output-type '(file progn t))
(cdr (cdr rest))
+ (eql (length body) (cdr (car rest)))
(eq (car (nth 1 rest)) 'byte-discard)
(progn (setq rest (cdr rest)) t))))
(setq maycall nil) ; Only allow one real function call.
next prev parent reply other threads:[~2019-03-08 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 8:01 bug#34757: Invalid bytecode from byte compiler chuntaro
2019-03-08 13:18 ` Eli Zaretskii
2019-03-08 13:50 ` Michael Heerdegen
2019-03-08 14:36 ` Eli Zaretskii
2019-03-08 21:13 ` Pip Cet [this message]
2019-03-15 8:08 ` Eli Zaretskii
2019-03-15 14:08 ` Stefan Monnier
2019-03-15 19:40 ` Pip Cet
2019-03-15 20:30 ` Stefan Monnier
2019-03-16 16:51 ` Pip Cet
2019-06-13 11:44 ` Pip Cet
2019-07-27 21:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOqdjBcTM6Z5KYLeFj=wiX2DvB57wGn1uZL96Gqr=fGtXNAQ=A@mail.gmail.com' \
--to=pipcet@gmail.com \
--cc=34757@debbugs.gnu.org \
--cc=chuntaro@sakura-games.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.