From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: emacs-devel@gnu.org
Subject: Re: GC: cons sweeping and cons block size
Date: Fri, 06 Jul 2007 08:48:05 -0400 [thread overview]
Message-ID: <jwvzm293dnh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E83F4FB7-DF31-4E17-BAB2-E4F2148E024E@raeburn.org> (Ken Raeburn's message of "Fri\, 6 Jul 2007 07\:54\:46 -0400")
> (quoting David, who was quoting Stefan)
>>>> I haven't found the time to do it, but it would be good to get rid of
>>>> this situation and always place tags in the 3 LSB bits.
> It does appear to be the default for most systems, maybe all modern ones,
> but only when we compile with GCC. Are we confident no one is using Emacs
> on systems where we use a system malloc that doesn't do 8-
> byte alignment?
No. IIRC at least Mac OS 9's malloc doesn't do 8-byte alignment.
By getting rid of the MSB tags I meant write the code to handle the case
where malloc doesn't return multiples of 8 and where we can't use GCC's
alignment attribute to force alignment on static (and/or stack structures).
> We could do a USE_LSB_TAG variant of the union, to get more address space
> back but keep the paranoid type checking capability.
If we can really get the exact same performance, maybe it's a good idea, but
since it's only really useful at compile-time, it's quite sufficient to
compile the source every once in a while with the USE_LISP_UNION_TYPE flag.
Stefan
next prev parent reply other threads:[~2007-07-06 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 6:43 GC: cons sweeping and cons block size dmantipov
2007-07-05 14:06 ` Stefan Monnier
2007-07-05 14:42 ` David Kastrup
2007-07-05 16:02 ` Stefan Monnier
2007-07-06 11:54 ` Ken Raeburn
2007-07-06 12:48 ` Stefan Monnier [this message]
[not found] <E1I5ktS-0001uQ-Uc@monty-python.gnu.org>
2007-07-03 20:22 ` Jonathan Yavner
2007-07-05 1:29 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2007-07-03 15:16 Dmitry Antipov
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=jwvzm293dnh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=raeburn@raeburn.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 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.