Change "Machien Integer Type Information."
Chagne to "AOT and JIT" description.
Change-Id: I4df1c49a3aa2f8e7606a0299afc66c44adc76397
diff --git a/README.html b/README.html
index 8c11bcf..0eda6a2 100644
--- a/README.html
+++ b/README.html
@@ -4,7 +4,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.6: http://docutils.sourceforge.net/" />
-<title>libbcc: A Versatile Bitcode Execution Engine</title>
+<title>libbcc: A Versatile Bitcode Execution Engine for Mobile Devices</title>
<style type="text/css">
/*
@@ -304,19 +304,23 @@
</style>
</head>
<body>
-<div class="document" id="libbcc-a-versatile-bitcode-execution-engine">
-<h1 class="title">libbcc: A Versatile Bitcode Execution Engine</h1>
+<div class="document" id="libbcc-a-versatile-bitcode-execution-engine-for-mobile-devices">
+<h1 class="title">libbcc: A Versatile Bitcode Execution Engine for Mobile Devices</h1>
<div class="section" id="introduction">
<h1>Introduction</h1>
<p>libbcc is an LLVM bitcode execution engine that compiles the bitcode
-to an in-memory executable.</p>
+to an in-memory executable. libbcc is versatile because:</p>
+<ul class="simple">
+<li>it implements both AOT (Ahead-of-Time) and JIT (Just-in-Time) compilation.</li>
+<li>Android devices demand fast start-up time, small size and high performance.</li>
+</ul>
<p>libbcc provides:</p>
<ul class="simple">
-<li>a <em>just-in-time (JIT) bitcode compiler</em>, which translates the bitcode into
+<li>a <em>just-in-time bitcode compiler</em>, which translates the bitcode into
machine code</li>
<li>a <em>caching mechanism</em>, which can:<ul>
-<li>after the compilation, serialize the in-memory executable into a cache file.
+<li>after each compilation, serialize the in-memory executable into a cache file.
Note that the compilation is triggered by a cache miss.</li>
<li>load from the cache file upon cache-hit.</li>
</ul>
@@ -329,7 +333,7 @@
<li>libbcc strives to balance between library size, launch time and
steady-state performance:<ul>
<li>The size of libbcc is aggressively reduced for mobile devices.
-We customize and we don't use Execution Engine.</li>
+We customize and we don't use the default Execution Engine from upstream.</li>
<li>To reduce launch time, we support caching of binaries.</li>
<li>For steady-state performance, we enable VFP3 and aggressive
optimizations.</li>
@@ -375,8 +379,9 @@
Here is the brief description of each sections:</p>
<ul class="simple">
<li><strong>Header</strong> (OBCC_Header) - The header of a cache file. It contains the
-magic word, version, machine integer type information, and the size
-and the offset of other sections. The header section is guaranteed
+magic word, version, machine integer type information (the endianness,
+the size of off_t, size_t, and ptr_t), and the size
+and offset of other sections. The header section is guaranteed
to be at the beginning of the cache file.</li>
<li><strong>String Pool</strong> (OBCC_StringPool) - A collection of serialized variable
length strings. The strp_index in the other part of the cache file