From: Kenichi Handa <handa@m17n.org>
Cc: d.love@dl.ac.uk, emacs-devel@gnu.org
Subject: Re: synchronizing emacs-unicode branch to HEAD
Date: Tue, 16 Sep 2003 11:27:48 +0900 (JST) [thread overview]
Message-ID: <200309160227.LAA08700@etlken.m17n.org> (raw)
In-Reply-To: <je65k2p1wb.fsf@sykes.suse.de> (message from Andreas Schwab on Tue, 09 Sep 2003 14:44:20 +0200)
In article <je65k2p1wb.fsf@sykes.suse.de>, Andreas Schwab <schwab@suse.de> writes:
> Kenichi Handa <handa@m17n.org> writes:
>> I think we can test if c_functions is GC clean or not by
>> setting and resetting abort_on_gc before and after calling
>> that function. Could you do that and verify it?
> I'll try.
>> As I don't have ia64 machine, I can't test it.
> You can force use of GCPRO on any machine.
Ah! You are right. Anyway, I found that you already
commited a proper fix. Thank you.
Dave Love <d.love@dl.ac.uk> writes:
> If you mean to do gcpro only when it's calling Lisp or specific C, I
> doubt that it is worth the trouble, especially as it could break with
> a newly-defined c_function.
> I don't think it's worth worrying about optimizing use of gcpro.
> There are probably no modern systems where it can't be turned off if
> anyone cares, at least with gcc.
Ok, I see.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-09-16 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 23:32 synchronizing emacs-unicode branch to HEAD Kenichi Handa
2003-09-09 9:59 ` Andreas Schwab
2003-09-09 12:12 ` Kenichi Handa
2003-09-09 12:44 ` Andreas Schwab
2003-09-16 2:27 ` Kenichi Handa [this message]
2003-09-09 19:04 ` Dave Love
2003-09-09 19:02 ` Dave Love
2003-09-09 19:51 ` Andreas Schwab
2003-09-09 20:32 ` Miles Bader
2003-09-10 1:15 ` Kenichi Handa
2003-09-10 2:25 ` Miles Bader
2003-09-11 9:21 ` Dave Love
2003-09-11 18:28 ` Eli Zaretskii
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=200309160227.LAA08700@etlken.m17n.org \
--to=handa@m17n.org \
--cc=d.love@dl.ac.uk \
--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).