all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
	 Dmitry Antipov <dmantipov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] trunk r117941: Default to stack objects on non-GNU/Linux, non-DOS_NT platforms.
Date: Thu, 25 Sep 2014 12:08:05 -0700	[thread overview]
Message-ID: <54246815.7030301@cs.ucla.edu> (raw)
In-Reply-To: <jwviokb1smu.fsf-monnier+emacs@gnu.org>

On 09/25/2014 11:12 AM, Stefan Monnier wrote:
> I saw this extra checking in
> local_cons, I figured this is going to kill too much of the
> performance gain.

I agree that the performance gains are iffy, and would like to see some 
measurements here.

If it's any consolation, in some cases the new MAX_ALLOCA checking is 
optimized away.  For example, other_buffer_safely calls 
build_local_string twice, both with constant literals, and in both cases 
my compiler (GCC 4.9.1 x86-64) deduces that there's no need to check for 
MAX_ALLOCA, and generates code that creates the Lisp string on the stack 
unconditionally.



  reply	other threads:[~2014-09-25 19:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  8:15 [Emacs-diffs] trunk r117941: Default to stack objects on non-GNU/Linux, non-DOS_NT platforms Eli Zaretskii
2014-09-25  9:51 ` Dmitry Antipov
2014-09-25 10:14   ` Eli Zaretskii
2014-09-25 12:52   ` Stefan Monnier
2014-09-25 16:12     ` Dmitry Antipov
2014-09-25 18:12       ` Stefan Monnier
2014-09-25 19:08         ` Paul Eggert [this message]
2014-09-25  9:52 ` Eli Zaretskii
2014-09-25 16:06 ` Paul Eggert
2014-09-25 16:48   ` Eli Zaretskii
2014-09-25 18:46     ` Paul Eggert
2014-09-25 19:16       ` Eli Zaretskii
2014-09-25 20:56         ` 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=54246815.7030301@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=dmantipov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.