summaryrefslogtreecommitdiffstats
path: root/Misc
diff options
context:
space:
mode:
authorMichael W. Hudson <mwh@python.net>2005-01-18 15:53:59 (GMT)
committerMichael W. Hudson <mwh@python.net>2005-01-18 15:53:59 (GMT)
commit46e6d92dc1c37e6e2f0fe9bec221e355b82d7b88 (patch)
tree010a56e7661924ad30da8d7a18e4f79a839348fa /Misc
parent969f485cba75c017d55a4dad450f5e0331b49359 (diff)
downloadcpython-46e6d92dc1c37e6e2f0fe9bec221e355b82d7b88.zip
cpython-46e6d92dc1c37e6e2f0fe9bec221e355b82d7b88.tar.gz
cpython-46e6d92dc1c37e6e2f0fe9bec221e355b82d7b88.tar.bz2
tweaks, small updates
Diffstat (limited to 'Misc')
-rw-r--r--Misc/SpecialBuilds.txt18
1 files changed, 9 insertions, 9 deletions
diff --git a/Misc/SpecialBuilds.txt b/Misc/SpecialBuilds.txt
index 3e05f81..1919e66 100644
--- a/Misc/SpecialBuilds.txt
+++ b/Misc/SpecialBuilds.txt
@@ -207,14 +207,14 @@ sys.getcounts()
---------------------------------------------------------------------------
LLTRACE introduced well before 1.0
-Compile in support of Low Level TRACE-ing of the main interpreter loop.
+Compile in support for Low Level TRACE-ing of the main interpreter loop.
-When this preprocessor symbol is defined, before eval_frame
-(eval_code2 before 2.2) executes a frame's code it checks the frame's
-global namespace for a variable "__lltrace__". If such a variable is
-found, mounds of information about what the interpreter is doing are
-sprayed to stdout, such as every opcode and opcode argument and values
-pushed onto and popped off the value stack.
+When this preprocessor symbol is defined, before PyEval_EvalFrame
+(eval_frame in 2.3 and 2.2, eval_code2 before that) executes a frame's code
+it checks the frame's global namespace for a variable "__lltrace__". If
+such a variable is found, mounds of information about what the interpreter
+is doing are sprayed to stdout, such as every opcode and opcode argument
+and values pushed onto and popped off the value stack.
Not useful very often, but very useful when needed.
@@ -245,8 +245,8 @@ that uses GCC (i.e. OS X and linux/ppc).
On the PowerPC the rate at which the time base register is incremented
is not defined by the architecture specification, so you'll need to
-find the manual for your specific processor. For the 750CX, 750CXe,
-750FX (all sold as the G3) we find:
+find the manual for your specific processor. For the 750CX, 750CXe
+and 750FX (all sold as the G3) we find:
The time base counter is clocked at a frequency that is
one-fourth that of the bus clock.