From: Nicholas Clark <nick@ccl4.org>
Date: Sat, 17 Sep 2005 18:34:37 +0000 (+0000)
Subject: Add ordering of "global" variables to TODO
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=0f788cd2167eac467cb834bf10fb461045b10ece;p=p5sagit%2Fp5-mst-13.2.git

Add ordering of "global" variables to TODO

p4raw-id: //depot/perl@25443
---

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 0caa728..4fec644 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -256,6 +256,21 @@ such that it's trivial for the Pumpking to flag "this is an official release"
 when making a tarball, yet leave the default source saying "I'm not the
 official release".
 
+=head2 Ordering of "global" variables.
+
+F<thrdvar.h> and F<intrpvarh> define the "global" variables that need to be
+per-thread under ithreads, where the variables are actually elements in a
+structure. As C dictates, the variables must be laid out in order of
+declaration. There is a comment
+C</* Important ones in the first cache line (if alignment is done right) */>
+which implies that at some point in the past the ordering was carefully chosen
+(at least in part). However, it's clear that the ordering is less than perfect,
+as currently there are things such as 7 C<bool>s in a row, then something
+typically requiring 4 byte alignment, and then an odd C<bool> later on.
+(C<bool>s are typically defined as C<char>s). So it would be good for someone
+to review the ordering of the variables, to see how much alignment padding can
+be removed.
+
 =head2 bincompat functions
 
 There are lots of functions which are retained for binary compatibility.