[llvm-commits] CVS: reopt/docs/ReoptUsersGuide.rtf

[Brian Gaeke]

Changes in directory reopt/docs:

ReoptUsersGuide.rtf updated: 1.2 -> 1.3
---
Log message:

We don't use procfs anymore.


---
Diffs of the changes:  (+7 -7)

Index: reopt/docs/ReoptUsersGuide.rtf
diff -u reopt/docs/ReoptUsersGuide.rtf:1.2 reopt/docs/ReoptUsersGuide.rtf:1.3
--- reopt/docs/ReoptUsersGuide.rtf:1.2	Tue Oct 12 13:38:32 2004
+++ reopt/docs/ReoptUsersGuide.rtf	Tue Oct 12 14:56:17 2004
@@ -3,7 +3,7 @@
 \f3\fmodern\fcharset77 Courier;\f4\fmodern\fcharset77 Courier-Oblique;\f5\fswiss\fcharset77 Helvetica-Oblique;
 \f6\fmodern\fcharset77 Courier-Bold;}
 {\colortbl;\red255\green255\blue255;}
-\margl1440\margr1440\vieww12000\viewh15840\viewkind0
+\margl1440\margr1440\vieww15300\viewh18220\viewkind0
 \deftab720
 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardeftab720\ql\qnatural
 
@@ -423,7 +423,7 @@
 \f3 \ul reopt/lib/TraceJIT/TraceJITEmitter.cpp
 \f0 \ul )\ulnone \
 \
-The unpacked trace code is emitted into the memory used by the trace cache using the VirtualMem abstraction, which implements reads and writes into the process's executable address space using the /proc filesystem. Once the trace has been emitted, the beginning of the SLI trace is overwritten with a branch to the beginning of the optimized trace, effectively disabling the SLI trace from further execution and enabling the optimized trace instead; control then returns from the second-level trigger function, which is invariably followed by a branch into the optimized trace.\
+The unpacked trace code is emitted into the memory used by the trace cache using the VirtualMem abstraction, which uses the mprotect() system call to lazily add write permissions to executable memory pages before writing into them for the first time. Once the trace has been emitted, the beginning of the SLI trace is overwritten with a branch to the beginning of the optimized trace, effectively disabling the SLI trace from further execution and enabling the optimized trace instead; control then returns from the second-level trigger function, which is invariably followed by a branch into the optimized trace.\
 \
 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardeftab720\ql\qnatural
 
@@ -499,7 +499,7 @@
 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardeftab720\ql\qnatural
 
 \f3 \cf0 \ul \ulc0 ttftest
-\f0 \ul - a standalone TraceToFunction testing tool (
+\f0 \ul  - a standalone TraceToFunction testing tool (
 \f3 \ul reopt/tools/ttftest
 \f0 \ul )\ulnone \
 \
@@ -519,7 +519,7 @@
 \
 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardeftab720\ql\qnatural
 
-\f3 \cf0 ttftest
+\f3 \cf0 ttftest 
 \f0 will also run the LLVM Verifier on the TraceFunction, and exit with an exit code of 0 if the verifier passes. This is the basic strategy used for the automated TraceToFunction regression tests (
 \f3 reopt/test/TTFTestCases
 \f0  and 
@@ -529,7 +529,7 @@
 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardeftab720\ql\qnatural
 
 \f3 \cf0 \ul \ulc0 dumptrace
-\f0 \ul - list LLVM assembly for a trace's basic blocks (
+\f0 \ul  - list LLVM assembly for a trace's basic blocks (
 \f3 \ul reopt/tools/dumptrace
 \f0 \ul )\ulnone \
 \
@@ -540,13 +540,13 @@
 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardeftab720\ql\qnatural
 
 \f3 \cf0 dumptrace
-\f0 also highlights two sets of values for your inspection: the values used on the trace which are defined outside the trace, and the values defined inside the trace which are used outside the trace. (Note that these are often subsets of the live-in/out sets computed by TraceToFunction; if you want to see those, use 
+\f0  also highlights two sets of values for your inspection: the values used on the trace which are defined outside the trace, and the values defined inside the trace which are used outside the trace. (Note that these are often subsets of the live-in/out sets computed by TraceToFunction; if you want to see those, use 
 \f3 ttftest -print-live
 \f0 .)\
 \
 
 \f3 dumptrace
-\f0 requires the same 
+\f0  requires the same 
 \f3 -bc
 \f0  and 
 \f3 -trace