all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Gramiak <agrambot@gmail.com>
To: 35321@debbugs.gnu.org
Subject: bug#35321: [PATCH] * src/bytecode.c (exec_byte_code) Unroll Blist3 and Blist4
Date: Fri, 19 Apr 2019 08:41:43 -0600	[thread overview]
Message-ID: <87lg0683bs.fsf@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 174 bytes --]

Hopefully someone with experience in the byte compiler can affirm that
this is okay. It passes make check for me (outside of 1 flymake error
that occurs in master as well).


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: unroll --]
[-- Type: text/x-patch, Size: 797 bytes --]

From ba211b61d2c9e60935415f57b15511477132bccb Mon Sep 17 00:00:00 2001
From: Alexander Gramiak <agrambot@gmail.com>
Date: Fri, 19 Apr 2019 08:29:39 -0600
Subject: [PATCH] * src/bytecode.c (exec_byte_code) Unroll Blist3 and Blist4

---
 src/bytecode.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/bytecode.c b/src/bytecode.c
index 40977799bf..b38c21a464 100644
--- a/src/bytecode.c
+++ b/src/bytecode.c
@@ -884,12 +884,12 @@ exec_byte_code (Lisp_Object bytestr, Lisp_Object vector, Lisp_Object maxdepth,
 
 	CASE (Blist3):
 	  DISCARD (2);
-	  TOP = Flist (3, &TOP);
+	  TOP = list3 (TOP, top[1], top[2]);
 	  NEXT;
 
 	CASE (Blist4):
 	  DISCARD (3);
-	  TOP = Flist (4, &TOP);
+	  TOP = list4 (TOP, top[1], top[2], top[3]);
 	  NEXT;
 
 	CASE (BlistN):
-- 
2.21.0


             reply	other threads:[~2019-04-19 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 14:41 Alex Gramiak [this message]
2019-04-19 15:08 ` bug#35321: [PATCH] * src/bytecode.c (exec_byte_code) Unroll Blist3 and Blist4 Eli Zaretskii
2019-04-19 20:30   ` Alex Gramiak
2019-04-19 20:49     ` Eli Zaretskii
2019-04-19 21:31       ` Alex Gramiak
2019-04-20  6:20         ` Eli Zaretskii
2019-04-20 20:05           ` Stefan Monnier
2019-05-03  8:41             ` Eli Zaretskii
2019-06-23 17:36               ` Lars Ingebrigtsen

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=87lg0683bs.fsf@gmail.com \
    --to=agrambot@gmail.com \
    --cc=35321@debbugs.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.
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.