[llvm-commits] CVS: llvm-www/ProjectsWithLLVM/index.html

Misha Brukman brukman at cs.uiuc.edu
Wed May 12 18:53:02 PDT 2004


Changes in directory llvm-www/ProjectsWithLLVM:

index.html updated: 1.12 -> 1.13

---
Log message:

* Mention that Jello (which is the LLVM JIT) is now part of lli.
* Reduce extraneous space caused by placing <p> and </p> on lines by themselves


---
Diffs of the changes:  (+36 -49)

Index: llvm-www/ProjectsWithLLVM/index.html
diff -u llvm-www/ProjectsWithLLVM/index.html:1.12 llvm-www/ProjectsWithLLVM/index.html:1.13
--- llvm-www/ProjectsWithLLVM/index.html:1.12	Wed May 12 16:06:52 2004
+++ llvm-www/ProjectsWithLLVM/index.html	Wed May 12 18:53:24 2004
@@ -85,13 +85,13 @@
 compilation and execution details are taken care of by LLVM.</p>
 
 <p>Further information about XPS can be obtained at <a
-href="http://extprosys.sourceforge.net/">http://extprosys.sourceforge.net/</a>. This
-information is somewhat dated but may provide an overview.  XPS is getting a new
-home on the Internet soon. We'll update this link when its available.
-</p>
+href="http://extprosys.sourceforge.net/">http://extprosys.sourceforge.net/</a>.
+This information is somewhat dated but may provide an overview.  XPS is getting
+a new home on the Internet soon. We'll update this link when its available.</p>
 
 <!--=========================================================================-->
-<div class="www_sectiontitle">CS497YYZ: Hot Topics in Operating Systems (Fall 2003)</div>
+<div class="www_sectiontitle">CS497YYZ: Hot Topics in Operating Systems (Fall
+2003)</div>
 <!--=========================================================================-->
 
 <!-- _______________________________________________________________________ -->
@@ -138,26 +138,22 @@
 Brian Fahs
 </div>
 
-<p>
-"As every modern computer user has experienced, software updates and upgrades
-frequently require programs and sometimes the entire operating system to be
-restarted. This can be a painful and annoying experience. What if this common
-annoyance could be avoided completely or at least significantly reduced? Imagine
-only rebooting your system when you wanted to shut your computer down or only
-closing an application when you wanted rather than when an update occurs.  The
-purpose of this project is to investigate the potential of performing dynamic
-patching of executables and create a patching tool capable of automatically
-generating patches and applying them to applications that are already
-running. This project should answer questions like: How can dynamic updating be
-performed? What type of analysis is required? Can this analysis be effectively
-automated? What can be updated in the running executable (e.g., algorithms,
-organization, data, etc.)?"
-</p>
+<p>"As every modern computer user has experienced, software updates and
+upgrades frequently require programs and sometimes the entire operating system
+to be restarted. This can be a painful and annoying experience. What if this
+common annoyance could be avoided completely or at least significantly reduced?
+Imagine only rebooting your system when you wanted to shut your computer down or
+only closing an application when you wanted rather than when an update occurs.
+The purpose of this project is to investigate the potential of performing
+dynamic patching of executables and create a patching tool capable of
+automatically generating patches and applying them to applications that are
+already running. This project should answer questions like: How can dynamic
+updating be performed? What type of analysis is required? Can this analysis be
+effectively automated? What can be updated in the running executable (e.g.,
+algorithms, organization, data, etc.)?"</p>
 
-<p>
-Project report: <a href="2003-Fall-CS497YYZ-SPEDI.ps">PS</a>,
-<a href="2003-Fall-CS497YYZ-SPEDI.pdf">PDF</a>
-</p>
+<p>Project report: <a href="2003-Fall-CS497YYZ-SPEDI.ps">PS</a>, <a
+href="2003-Fall-CS497YYZ-SPEDI.pdf">PDF</a></p>
 
 
 <!--=========================================================================-->
@@ -181,25 +177,22 @@
 Joel Stanley, Bill Wendling
 </div>
 
-<p>
-"In this report we present implementation details, empirical performance data,
-and notable modifications to an algorithm for PRE based on [the 1999 TOPLAS
-SSAPRE paper].  In [the 1999 TOPLAS SSAPRE paper], a particular realization of
-PRE, known as SSAPRE, is described, which is more efficient than traditional PRE
-implementations because it relies on useful properties of Static
+<p>"In this report we present implementation details, empirical performance
+data, and notable modifications to an algorithm for PRE based on [the 1999
+TOPLAS SSAPRE paper].  In [the 1999 TOPLAS SSAPRE paper], a particular
+realization of PRE, known as SSAPRE, is described, which is more efficient than
+traditional PRE implementations because it relies on useful properties of Static
 Single-Assignment (SSA) form to perform dataflow analysis in a much more sparse
 manner than the traditional bit-vector-based approach.  Our implementation is
 specific to a SSA-based compiler infrastructure known as LLVM (Low-Level Virtual
-Machine)."
-</p>
+Machine)."</p>
 
-<p>
-Project report: <a href="2002-Fall-CS426-SSAPRE.ps">PS</a>,
-<a href="2002-Fall-CS426-SSAPRE.pdf">PDF</a>
-</p>
+<p>Project report: <a href="2002-Fall-CS426-SSAPRE.ps">PS</a>, <a
+href="2002-Fall-CS426-SSAPRE.pdf">PDF</a></p>
 
 <!--=========================================================================-->
-<div class="www_sectiontitle">CS497CZ: Dynamic Translation and Optimization (Spring 2002)</div>
+<div class="www_sectiontitle">CS497CZ: Dynamic Translation and Optimization
+(Spring 2002)</div>
 <!--=========================================================================-->
 
 <!-- _______________________________________________________________________ -->
@@ -211,8 +204,7 @@
 <a href="http://www.students.uiuc.edu/~gaeke/">Brian Gaeke</a>
 </div>
 
-<p>
-"We present the design and implementation of Jello, a <i>retargetable</i>
+<p>"We present the design and implementation of Jello, a <i>retargetable</i>
 Just-In-Time (JIT) compiler for the Intel IA32 architecture.  The input to Jello
 is a C program statically compiled to Low-Level Virtual Machine (LLVM) bytecode.
 Jello takes advantage of the features of the LLVM bytecode representation to
@@ -224,17 +216,12 @@
 target-independent, making the JIT easily retargetable to new platforms without
 changing the code generator.  Jello's ultimate goal is to provide a flexible
 host for future research in runtime optimization for programs written in
-languages which are traditionally compiled statically."
-</p>
-
-<p>
-Note that Jello eventually evolved into the current LLVM JIT.
-</p>
+languages which are traditionally compiled statically."</p>
 
-<p>
-Project report: <a href="2002-Spring-CS497CZ-Jello.ps">PS</a>,
-<a href="2002-Spring-CS497CZ-Jello.pdf">PDF</a>
-</p>
+<p>Note that Jello eventually evolved into the current LLVM JIT, which is part
+of the tool <b>lli</b>.</p>
 
+<p>Project report: <a href="2002-Spring-CS497CZ-Jello.ps">PS</a>, <a
+href="2002-Spring-CS497CZ-Jello.pdf">PDF</a></p>
 
 <!--#include virtual="../footer.incl" --></html>





More information about the llvm-commits mailing list