Author: mikhail.naganov
Date: Tue Jun 16 06:08:29 2009
New Revision: 2190

Modified:
    wiki/V8Oprofile.wiki

Log:
Minor corrections of typos.

Modified: wiki/V8Oprofile.wiki
==============================================================================
--- wiki/V8Oprofile.wiki        (original)
+++ wiki/V8Oprofile.wiki        Tue Jun 16 06:08:29 2009
@@ -2,10 +2,10 @@

  = Introduction =

-V8 supports profiling using OProfile through a OProfile agent for handling  
dynamically generated code together with the staticly compiled code.
+V8 supports profiling using OProfile through an OProfile agent for  
handling dynamically generated code together with the statically compiled  
code.

  = Requirements =
-OProfile version 0.9.4 or higher is required as this is the first version  
with support for dynamically generated (through the JIT API). As V8  
currently support only 32-bit a 32-bit version of the OProfile and its  
agent library is required. This includes the libraries that OProfile  
depends in 32-bit as well.
+OProfile version 0.9.4 or higher is required as this is the first version  
with support for dynamically generated code (through the JIT API). As V8 is  
currently only 32-bit, a 32-bit version of the OProfile and its agent  
library is required. This includes the libraries that OProfile depends on  
to be 32-bit as well.

  = Build =

@@ -23,7 +23,7 @@
  ./shell --prof=oprofile script.js
  }}}

-OProfile currently doesn't support code moving around. To avoid this  
happening in V8 whilr profiling the `--oprofile` flag automatically  
disables code moving by setting the `--never-compact` flag.
+OProfile currently doesn't support code moving around. To avoid this  
happening in V8 while profiling the `--oprofile` flag automatically  
disables code moving by setting the `--never-compact` flag.

  = OProfile Utility Scripts =

@@ -41,7 +41,7 @@
  tools/oprofile/shutdown
  }}}

-For all the commands taking an executable the executable is expected to be
+For all the commands taking an executable the latter is expected to be
  a binary using V8. If no executable is specified the release mode V8 shell
  will be used.


--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to