unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Help with adding an auxiliary bytecode table
Date: Sun, 21 Apr 2019 00:11:25 -0400	[thread overview]
Message-ID: <jwvsguct2z7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87pnpj9uod.fsf@gmail.com

> I've attached a diff below that adds an auxiliary optable to bytecode.c
> and attempts to integrate it into bytecode.el. I can run emacs -Q with
> it, but when I run it with my configuration I get the following in
> stderr:
>
>   Invalid function: ((bytecomp "Wrong type argument: arrayp, nil" :error
>   "*Compile-Log*"))

Use the debugger so you can get a more complete backtrace.

> My initial reaction is that the stale bytecode is somehow incompatible,

What/which stale bytecode?

> The problem is that since memq is a bytecode operation, it turns out
> to be faster than vector-memq for small input

Why is that a problem?

> unless I make sure that memq isn't turned into a bytecode op.
> So since the current space in the lookup table is limited, I figured
> that a prefix command that looks up in a secondary table would be
> a good solution.

We don't have too many bytecodes left, indeed, but there are still some,
IIRC, so it's not indispensable to go a 2-byte bytecodes.


        Stefan




  parent reply	other threads:[~2019-04-21  4:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 15:53 Help with adding an auxiliary bytecode table Alex Gramiak
2019-04-18 17:07 ` Paul Eggert
2019-04-18 20:47   ` Alex Gramiak
2019-04-21  4:11 ` Stefan Monnier [this message]
2019-04-21 19:17   ` Help with adding new setq-based bytecodes (was: Help with adding an auxiliary bytecode table) Alex Gramiak
2019-04-21 20:22     ` Help with adding new setq-based bytecodes 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=jwvsguct2z7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@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 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).