all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
Cc: emacs-unicode@gnu.org, jan.h.d@swipnet.se, emacs-devel@gnu.org,
	duncanmak@gmail.com, Kenichi Handa <handa@m17n.org>
Subject: Re: Crash building unicode2, NSTATICS too low, pure space overflow.
Date: Fri, 04 Aug 2006 11:09:55 +0200	[thread overview]
Message-ID: <jeodv027fg.fsf@sykes.suse.de> (raw)
In-Reply-To: <E1G8ifC-0003P8-LR@fencepost.gnu.org> (Richard Stallman's message of "Thu, 03 Aug 2006 15:15:22 -0400")

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.

Since staticvec is statically allocated there is no need to care for
malloc overhead.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2006-08-04  9:09 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
2006-08-04  9:09       ` Andreas Schwab [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jeodv027fg.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=duncanmak@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-unicode@gnu.org \
    --cc=handa@m17n.org \
    --cc=jan.h.d@swipnet.se \
    /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.