From: "Bauer, Christoph" <Christoph.Bauer@lms-gmbh.de>
To: caml-list@inria.fr
Subject: AW: [Caml-list] The tag bit
Date: Thu, 12 Aug 2004 17:22:53 +0200 [thread overview]
Message-ID: <D981925B4F2CD611870300E0184CEE9B0157F260@mail.lms-gmbh.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
> Well, I can see several reasons :
> * processors like powers of two, especially when it comes
> to the size
> of a memory address, because of cache issues, so you'd better
> make it 32
> or 64 words than 33 or 65.
> * If the tag bit can be anywhere in a word you have to spend extra
> time to extract it, whereas when it is at a fixed place,
> especially LSB
> or MSB, it is very cheap and easy.
> * You would need two registers to access a value and its
> tag instead
> of one, and registers are very precious, at least on IA-32
> architectures.
But who needs the tag bit? Only the garbage collector. Maybe it's
an advantage to see 32 tag bits as a whole, e.g. the question
"does the block contains any pointer" can be calculated bit-parallel.
Anyway the garbage collector could works on blocks and needs
just one additional memory access per block.
Regards,
Christoph Bauer
[-- Attachment #2: Type: text/html, Size: 1807 bytes --]
next reply other threads:[~2004-08-12 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 15:22 Bauer, Christoph [this message]
2004-08-13 3:53 ` Jacques Garrigue
2004-08-13 12:58 ` Christophe Raffalli
2004-08-13 13:14 ` [Caml-list] Other GC in ML family ? Diego Olivier Fernandez Pons
2004-08-13 13:24 ` AW: [Caml-list] The tag bit Andreas Rossberg
2004-08-13 14:32 ` T. Kurt Bond
2004-08-13 14:41 ` AW: [Caml-list] Conservative GC T. Kurt Bond
2004-08-13 16:14 ` AW: [Caml-list] The tag bit Ville-Pertti Keinonen
2004-08-13 14:28 ` skaller
2004-08-13 15:44 ` Christophe Raffalli
2004-08-13 15:40 ` Brian Hurt
2004-08-13 13:43 Ennals, Robert
2004-08-13 14:58 Ennals, Robert
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=D981925B4F2CD611870300E0184CEE9B0157F260@mail.lms-gmbh.de \
--to=christoph.bauer@lms-gmbh.de \
--cc=caml-list@inria.fr \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox