From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kenichi Handa <handa@gnu.org>
Cc: eliz@gnu.org, cyd@gnu.org, emacs-devel@gnu.org
Subject: Re: Feature freeze on October 1
Date: Thu, 27 Sep 2012 08:57:23 -0400 [thread overview]
Message-ID: <jwv626zy6nx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878vbval16.fsf@gnu.org> (Kenichi Handa's message of "Thu, 27 Sep 2012 18:10:29 +0900")
>> > Your memory is fine. The workaround code is in ralloc.c and in
>> > maybe_unify_char. But since we still call maybe_unify_char in
>> > decode_char, I don't think we can remove those workarounds yet, can
>> > we?
>> Are there calls to decode_char which aren't prepared to run Elisp code?
> maybe_unify_char doesn't run Elisp code but allocates a Lisp
> vector and a Lisp chartable via load_charset.
Oh, indeed, I see it should not be able to run arbitrary Elisp, so the
damage is a bit more limited.
> And I'm not sure that all calls to decode_char are prepared
> to buffer/string relocation.
String relocation only happens during GC, which normally only happens
during Elisp evaluation, so that shouldn't be an issue.
But, yes, it seems that ccl.c and maybe coding.c both have uses of
decode_char where buffer relocation can cause problems
(CODING_DECODE_CHAR seems to try and handle it explicitly, but I'm not
sure it's sufficient).
Stefan
next prev parent reply other threads:[~2012-09-27 12:57 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 1:55 Feature freeze on October 1 Chong Yidong
2012-09-16 9:55 ` Daniel Colascione
2012-09-16 14:48 ` Stefan Monnier
2012-09-16 15:30 ` David Engster
2012-09-16 19:04 ` Stefan Monnier
2012-09-16 19:17 ` David Engster
2012-09-26 20:24 ` CEDET merge (was: Feature freeze on October 1) David Engster
2012-09-30 13:55 ` CEDET merge David Engster
2012-09-30 14:10 ` David Engster
2012-09-30 18:58 ` Glenn Morris
2012-09-30 19:17 ` Paul Eggert
2012-10-01 0:16 ` Glenn Morris
2012-10-01 3:44 ` Chong Yidong
2012-10-01 11:44 ` Eric M. Ludlam
2012-10-01 15:17 ` David Engster
2012-10-01 17:48 ` Chong Yidong
2012-10-01 17:56 ` Chong Yidong
2012-10-02 15:24 ` Chong Yidong
2012-10-04 19:32 ` David Engster
2012-10-06 11:19 ` Chong Yidong
2012-10-06 11:30 ` David Engster
2012-10-06 14:24 ` Chong Yidong
2012-10-06 14:54 ` Stefan Monnier
2012-10-06 17:29 ` David Engster
2012-10-06 18:10 ` Stefan Monnier
2012-10-07 11:19 ` David Engster
2012-10-06 23:31 ` Glenn Morris
2012-10-07 1:15 ` Glenn Morris
2012-10-07 11:03 ` David Engster
2012-10-27 14:40 ` David Engster
2012-10-28 18:50 ` Glenn Morris
2012-11-17 3:23 ` Glenn Morris
2012-11-18 15:42 ` David Engster
2012-11-20 2:45 ` Glenn Morris
2012-11-21 13:09 ` Chong Yidong
2012-10-07 20:50 ` David Engster
2012-11-08 12:32 ` Alex Ott
2012-09-16 17:55 ` Feature freeze on October 1 Bastien
2012-09-17 16:07 ` Eli Zaretskii
2012-09-17 16:54 ` Stefan Monnier
2012-09-17 18:22 ` Eli Zaretskii
2012-09-17 19:36 ` Stefan Monnier
2012-09-21 12:40 ` Eli Zaretskii
2012-09-21 16:34 ` Stefan Monnier
2012-09-23 2:05 ` Kenichi Handa
2012-09-24 14:40 ` Eli Zaretskii
2012-09-25 7:06 ` Eli Zaretskii
2012-09-25 12:12 ` Kenichi Handa
2012-09-25 12:46 ` Eli Zaretskii
2012-09-26 13:57 ` Kenichi Handa
2012-09-26 14:41 ` Eli Zaretskii
2012-09-26 19:47 ` Stefan Monnier
2012-09-27 9:10 ` Kenichi Handa
2012-09-27 12:57 ` Stefan Monnier [this message]
2012-09-30 15:27 ` Kenichi Handa
2012-09-30 19:57 ` Stefan Monnier
2012-09-25 13:12 ` Stefan Monnier
2012-09-19 13:11 ` Tassilo Horn
2012-09-20 18:22 ` Stefan Merten
2012-09-21 3:07 ` Chong Yidong
2012-09-21 5:45 ` Leo
2012-09-21 7:35 ` Eli Zaretskii
2012-09-21 9:06 ` Chong Yidong
2012-09-21 13:15 ` Stefan Monnier
2012-09-21 16:27 ` Stephen J. Turnbull
2012-09-23 9:35 ` Stefan Merten
2012-09-23 15:31 ` 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=jwv626zy6nx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@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).