unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Pure space overflows
Date: Sat, 22 Jan 2022 19:02:49 +0800	[thread overview]
Message-ID: <878rv8uj6u.fsf@yahoo.com> (raw)
In-Reply-To: <83v8ycm54l.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Jan 2022 12:33:46 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Po Lu <luangruo@yahoo.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sat, 22 Jan 2022 17:38:25 +0800
>> 
>> > And why BASE_PURESIZE and not SYSTEM_PURESIZE_EXTRA for those
>> > configurations?
>> 
>> Isn't that a relic from when we had separate headers for each machine
>> and configuration?
>
> No, not yet a relic.
>
>> I couldn't find anywhere they are set today.
>
> See src/conf_post.h.

I wonder if the following code being under an MSDOS conditional is an
oversight, since it mentions GNU/Linux:

  #ifdef HAVE_X_WINDOWS
  /* We need a little extra space, see ../../lisp/loadup.el and the
     commentary below, in the non-X branch.  The 140KB number was
     measured on GNU/Linux and on MS-Windows.  */
  #define SYSTEM_PURESIZE_EXTRA (-170000+140000)

Thanks.



  reply	other threads:[~2022-01-22 11:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pmokustt.fsf.ref@yahoo.com>
2022-01-22  7:34 ` Pure space overflows Po Lu
2022-01-22  8:50   ` Eli Zaretskii
2022-01-22  9:38     ` Po Lu
2022-01-22 10:33       ` Eli Zaretskii
2022-01-22 11:02         ` Po Lu [this message]
2022-01-22 11:13           ` Eli Zaretskii
2022-01-22 11:18             ` Eli Zaretskii
2022-01-22 11:19             ` Po Lu
2022-01-23  8:10               ` Po Lu
2022-01-23  8:16                 ` Eli Zaretskii
2022-01-23  9:28                   ` Po Lu
2022-01-23 11:16                     ` Eli Zaretskii
2022-01-23 12:22                       ` Andreas Schwab
2022-01-23 12:39                         ` Po Lu
2022-01-23 13:03                           ` Andreas Schwab
2022-01-23 13:26                             ` Po Lu
2022-01-23 13:35                               ` Andreas Schwab
2022-01-24  0:39                                 ` Po Lu

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=878rv8uj6u.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --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).