From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117912: Minor improvements to new stack-allocated Lisp objects.
Date: Sun, 21 Sep 2014 22:40:11 -0700 [thread overview]
Message-ID: <541FB63B.4070403@cs.ucla.edu> (raw)
In-Reply-To: <jwv7g0w9rbk.fsf-monnier+emacsdiffs@gnu.org>
Stefan Monnier wrote:
> I'm already doubtful that the local_* thingies will be useful, so
> I think distinguishing between local_* and scoped_* is way beyond the
> limit of diminishing returns.
The more I look at it the more I think local_cons and local_list* are
mistakes and should be discarded.
For example, build_desired_tool_bar_string has a loop, each iteration of
which creates temporaries; here local_list4 could exhaust the stack
whereas scoped_list4 is fine, and trunk bzr 117912 fixed that by
replacing local_list4 with scoped_list4. There appear to be similar
problems in every function that currently uses local_cons or
local_list*, so I'm thinking we should remove these macros and go back
to Fcons and list*.
We should also audit uses of make_local_vector, make_local_string, and
build_local_string to make sure that none of them are in loops that
could blow the stack. I think most uses of these are OK but some are
questionable.
If there's significant doubt whether the local_* and scoped_* thingies
are useful perhaps we should simply remove all of them....
next prev parent reply other threads:[~2014-09-22 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XVpwf-0005xe-7w@vcs.savannah.gnu.org>
2014-09-22 5:08 ` [Emacs-diffs] trunk r117912: Minor improvements to new stack-allocated Lisp objects Stefan Monnier
2014-09-22 5:40 ` Paul Eggert [this message]
2014-09-22 6:42 ` Dmitry Antipov
2014-09-22 8:19 ` Dmitry Antipov
2014-09-22 12:57 ` Stefan Monnier
2014-09-22 15:00 ` Eli Zaretskii
2014-09-22 14:44 ` Eli Zaretskii
2014-09-22 15:32 ` Paul Eggert
2014-09-22 16:04 ` Dmitry Antipov
2014-09-22 19:09 ` Eli Zaretskii
2014-09-23 5:53 ` Paul Eggert
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=541FB63B.4070403@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--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.