From: Kenichi Handa <handa@m17n.org>
Cc: emacs-unicode@gnu.org, duncanmak@gmail.com, rms@gnu.org,
emacs-devel@gnu.org
Subject: Re: Crash building unicode2, NSTATICS too low, pure space overflow.
Date: Mon, 07 Aug 2006 15:46:12 +0900 [thread overview]
Message-ID: <E1G9ysO-0004KE-00@etlken> (raw)
In-Reply-To: <44D6DCA0.7010308@swipnet.se> (message from Jan Djärv on Mon, 07 Aug 2006 08:24:32 +0200)
In article <44D6DCA0.7010308@swipnet.se>, Jan Djärv <jan.h.d@swipnet.se> writes:
> Kenichi Handa skrev:
>> In article <E1G8ifC-0003P8-LR@fencepost.gnu.org>, Richard
>> Stallman <rms@gnu.org> writes:
>>
>>> 1026 is 0x402, 1280 is 0x500. What is the good value
>>> for NSTATICS this time; 0x600 or 0x602?
>>
>>> Try 0x7f0. That should fit nicely in a block that
>>> malloc can get with no wasted space.
>>
>> Thank you. I've just installed that change.
> I don't see this change in HEAD or emacs-unicode2. Where
> did you check it in?
Sorry, I've committed the change surely this time (not to
0x7f0 but to 0x600 according to this RMS's mail).
Richard Stallman <rms@gnu.org> writes:
> I had forgotten that. Since it is statically allocated,
> might as well just make it 0x600. It will last us another
> few years.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-08-07 6:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1G7kSB-0000Mi-00@etlken>
[not found] ` <44D19F77.4050904@swipnet.se>
2006-08-03 7:36 ` Crash building unicode2, NSTATICS too low, pure space overflow Kenichi Handa
2006-08-03 10:01 ` Jan Djärv
2006-08-03 19:15 ` Richard Stallman
2006-08-04 0:58 ` Kenichi Handa
2006-08-04 4:58 ` Richard Stallman
2006-08-07 6:24 ` Jan Djärv
2006-08-07 6:46 ` Kenichi Handa [this message]
2006-08-04 9:09 ` Andreas Schwab
2006-08-04 9:29 ` Duncan Mak
2006-08-04 10:05 ` David Kastrup
2006-08-04 16:14 ` Duncan Mak
2006-08-04 18:42 ` Richard Stallman
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=E1G9ysO-0004KE-00@etlken \
--to=handa@m17n.org \
--cc=duncanmak@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-unicode@gnu.org \
--cc=rms@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).