Mention in the exposition that lli can JIT on PowerPC now.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@18646 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html
index eb8d1d0b07ce64ab2242e254fe6ca9861a5fcc02..d23ac921302323008066109b51c38c6c44f5760d 100644 (file)
--- a/docs/GettingStarted.html
+++ b/docs/GettingStarted.html
@@ -1228,7 +1228,7 @@ information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
   can directly execute LLVM bytecode (although very slowly...). In addition
   to a simple interpreter, <tt>lli</tt> also has a tracing mode (entered by
   specifying <tt>-trace</tt> on the command line). Finally, for
   can directly execute LLVM bytecode (although very slowly...). In addition
   to a simple interpreter, <tt>lli</tt> also has a tracing mode (entered by
   specifying <tt>-trace</tt> on the command line). Finally, for

-  architectures that support it (currently only x86 and Sparc), by default,
+  architectures that support it (currently x86, Sparc, and PowerPC), by default,

   <tt>lli</tt> will function as a Just-In-Time compiler (if the
   functionality was compiled in), and will execute the code <i>much</i>
   faster than the interpreter.</dd>
   <tt>lli</tt> will function as a Just-In-Time compiler (if the
   functionality was compiled in), and will execute the code <i>much</i>
   faster than the interpreter.</dd>