From: Andreas Schwab <schwab@suse.de>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-unicode@gnu.org, emacs-devel@gnu.org,
Jason Rumney <jasonr@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Miles Bader <miles@gnu.org>
Subject: Re: unicode merge failures 2007-10-12
Date: Wed, 17 Oct 2007 02:04:48 +0200 [thread overview]
Message-ID: <jezlyi8v33.fsf@sykes.suse.de> (raw)
In-Reply-To: <200710122212.l9CMCD3r024677@oogie-boogie.ics.uci.edu> (Dan Nicolaescu's message of "Fri\, 12 Oct 2007 15\:12\:13 -0700")
Dan Nicolaescu <dann@ics.uci.edu> writes:
> Does anyone else see a too big data segment size for the unicode-2
> binary:
>
> size -f objs-HEAD/src/emacs objs-unicode-2/src/emacs
> text data bss dec hex filename
> 1534480 4031660 0 5566140 54eebc objs-HEAD/src/emacs
> 1656770 11663100 0 13319870 cb3ebe objs-unicode-2/src/emacs
>
> The first one is from CVS HEAD, the second is from unicode-2
Most of the increase can be attributed to heap usage (nearly fourfold),
whereas the size of pure space even decreased slightly.
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."
next prev parent reply other threads:[~2007-10-17 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 16:13 unicode merge failures 2007-10-12 Miles Bader
2007-10-11 22:35 ` Jason Rumney
2007-10-12 1:04 ` Stefan Monnier
2007-10-12 4:05 ` Stefan Monnier
2007-10-12 17:43 ` Stefan Monnier
2007-10-12 21:30 ` Dan Nicolaescu
2007-10-12 21:51 ` Miles Bader
2007-10-12 22:12 ` Dan Nicolaescu
2007-10-16 23:04 ` James Cloos
2007-10-17 0:04 ` Andreas Schwab [this message]
2007-10-17 1:04 ` Kenichi Handa
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=jezlyi8v33.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=emacs-unicode@gnu.org \
--cc=jasonr@gnu.org \
--cc=miles@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 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).