all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: 24100@debbugs.gnu.org
Subject: bug#24100: [PATCH 0/4] Some regex dead-code elimination
Date: Thu, 28 Jul 2016 19:00:28 +0200	[thread overview]
Message-ID: <1469725228-24151-1-git-send-email-mina86@mina86.com> (raw)

The first patch is just a minor cleanup, the rests bank on the
observation that Emacs only ever uses its own regex syntax.

Overall, this shrinks Emacs by over 60 kB and expecetdly also speeds
it up.

This patchest is put on top of my previous on from bug#24009.  The
whole branch can be seen at https://github.com/mina86/emacs/.

Unless there are objections, I’ve submit it in a week or so.

Michal Nazarewicz (4):
  Remove dead opcodes in regex bytecode
  Get rid of re_set_syntax
  Get rid of re_set_whitespace_regexp
  Hardcode regex syntax to remove dead code handling different syntax

 src/regex.c  | 101 ++++++++++++++++++++++++++++++++++-------------------------
 src/regex.h  |  20 ++++++++++--
 src/search.c |  17 +++-------
 3 files changed, 80 insertions(+), 58 deletions(-)

-- 
2.8.0.rc3.226.g39d4020






             reply	other threads:[~2016-07-28 17:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 17:00 Michal Nazarewicz [this message]
2016-07-28 18:07 ` bug#24100: [PATCH 1/4] Remove dead opcodes in regex bytecode Michal Nazarewicz
2016-07-28 18:07   ` bug#24100: [PATCH 2/4] Get rid of re_set_syntax Michal Nazarewicz
2016-07-28 18:07   ` bug#24100: [PATCH 3/4] Get rid of re_set_whitespace_regexp Michal Nazarewicz
2016-07-28 18:07   ` bug#24100: [PATCH 4/4] Hardcode regex syntax to remove dead code handling different syntax Michal Nazarewicz
2016-08-02 16:06 ` bug#24100: [PATCH 0/4] Some regex dead-code elimination Michal Nazarewicz

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=1469725228-24151-1-git-send-email-mina86@mina86.com \
    --to=mina86@mina86.com \
    --cc=24100@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.