[llvm-commits] CVS: llvm/www/docs/CommandLine.html LangRef.html OpenProjects.html
John Criswell
criswell at choi.cs.uiuc.edu
Thu Jun 26 16:44:21 PDT 2003
Changes in directory llvm/www/docs:
CommandLine.html updated: 1.9 -> 1.9.2.1
LangRef.html updated: 1.23 -> 1.23.2.1
OpenProjects.html updated: 1.6 -> 1.6.2.1
---
Log message:
Merged with mainline on Thursday, June 26, 2003.
---
Diffs of the changes:
Index: llvm/www/docs/CommandLine.html
diff -u llvm/www/docs/CommandLine.html:1.9 llvm/www/docs/CommandLine.html:1.9.2.1
--- llvm/www/docs/CommandLine.html:1.9 Mon Jun 2 23:40:06 2003
+++ llvm/www/docs/CommandLine.html Thu Jun 26 16:36:22 2003
@@ -94,8 +94,9 @@
<li>Speed: The CommandLine library is very quick and uses little resources. The
parsing time of the library is directly proportional to the number of arguments
parsed, not the the number of options recognized. Additionally, command line
-argument values are captured transparently into user defined variables, which
-can be accessed like any other variable (and with the same performance).<p>
+argument values are captured transparently into user defined global variables,
+which can be accessed like any other variable (and with the same
+performance).<p>
<li>Type Safe: As a user of CommandLine, you don't have to worry about
remembering the type of arguments that you want (is it an int? a string? a
@@ -183,24 +184,24 @@
Now that you are ready to support command line arguments, we need to tell the
system which ones we want, and what type of argument they are. The CommandLine
-library uses a declarative syntax to model cammand line arguments with the
-variable declarations that capture the parsed values. This means that for every
-command line option that you would like to support, there should be a variable
-declaration to capture the result. For example, in a compiler, we would like to
-support the unix standard '<tt>-o <filename></tt>' option to specify where
-to put the output. With the CommandLine library, this is represented like
-this:<p>
+library uses a declarative syntax to model command line arguments with the
+global variable declarations that capture the parsed values. This means that
+for every command line option that you would like to support, there should be a
+global variable declaration to capture the result. For example, in a compiler,
+we would like to support the unix standard '<tt>-o <filename></tt>' option
+to specify where to put the output. With the CommandLine library, this is
+represented like this:<p>
<pre><a name="value_desc_example">
<a href="#cl::opt">cl::opt</a><string> OutputFilename("<i>o</i>", <a href="#cl::desc">cl::desc</a>("<i>Specify output filename</i>"), <a href="#cl::value_desc">cl::value_desc</a>("<i>filename</i>"));
</pre><p>
-This declares a variable "<tt>OutputFilename</tt>" that is used to capture the
-result of the "<tt>o</tt>" argument (first parameter). We specify that this is
-a simple scalar option by using the "<tt><a href="#cl::opt">cl::opt</a></tt>"
-template (as opposed to the <a href="#list">"<tt>cl::list</tt>
-template</a>), and tell the CommandLine library that the data type that we are
-parsing is a string.<p>
+This declares a global variable "<tt>OutputFilename</tt>" that is used to
+capture the result of the "<tt>o</tt>" argument (first parameter). We specify
+that this is a simple scalar option by using the "<tt><a
+href="#cl::opt">cl::opt</a></tt>" template (as opposed to the <a
+href="#list">"<tt>cl::list</tt> template</a>), and tell the CommandLine library
+that the data type that we are parsing is a string.<p>
The second and third parameters (which are optional) are used to specify what to
output for the "<tt>--help</tt>" option. In this case, we get a line that looks
@@ -1495,7 +1496,7 @@
<address><a href="mailto:sabre at nondot.org">Chris Lattner</a></address>
<!-- Created: Tue Jan 23 15:19:28 CST 2001 -->
<!-- hhmts start -->
-Last modified: Mon Jun 2 23:39:44 CDT 2003
+Last modified: Sat Jun 21 16:45:29 CDT 2003
<!-- hhmts end -->
</font>
</body></html>
Index: llvm/www/docs/LangRef.html
diff -u llvm/www/docs/LangRef.html:1.23 llvm/www/docs/LangRef.html:1.23.2.1
--- llvm/www/docs/LangRef.html:1.23 Thu May 8 10:55:44 2003
+++ llvm/www/docs/LangRef.html Thu Jun 26 16:36:22 2003
@@ -295,7 +295,7 @@
<table border=1 cellspacing=0 cellpadding=4 align=center>
<tr><td><a name="t_signed">signed</td> <td><tt>sbyte, short, int, long, float, double</tt></td></tr>
<tr><td><a name="t_unsigned">unsigned</td><td><tt>ubyte, ushort, uint, ulong</tt></td></tr>
-<tr><td><a name="t_integral">integer</td><td><tt>ubyte, sbyte, ushort, short, uint, int, ulong, long</tt></td></tr>
+<tr><td><a name="t_integer">integer</td><td><tt>ubyte, sbyte, ushort, short, uint, int, ulong, long</tt></td></tr>
<tr><td><a name="t_integral">integral</td><td><tt>bool, ubyte, sbyte, ushort, short, uint, int, ulong, long</tt></td></tr>
<tr><td><a name="t_floating">floating point</td><td><tt>float, double</tt></td></tr>
<tr><td><a name="t_firstclass">first class</td><td><tt>bool, ubyte, sbyte, ushort, short,<br> uint, int, ulong, long, float, double, <a href="#t_pointer">pointer</a></tt></td></tr>
@@ -1193,9 +1193,10 @@
<h5>Example:</h5>
<pre>
<result> = shr int 4, ubyte %var <i>; yields {int}:result = 4 >> %var</i>
- <result> = shr int 4, ubyte 1 <i>; yields {int}:result = 2</i>
+ <result> = shr uint 4, ubyte 1 <i>; yields {uint}:result = 2</i>
<result> = shr int 4, ubyte 2 <i>; yields {int}:result = 1</i>
- <result> = shr int 4, ubyte 3 <i>; yields {int}:result = 0</i>
+ <result> = shr sbyte 4, ubyte 3 <i>; yields {sbyte}:result = 0</i>
+ <result> = shr sbyte -2, ubyte 1 <i>; yields {sbyte}:result = -1</i>
</pre>
@@ -1810,7 +1811,7 @@
<address><a href="mailto:sabre at nondot.org">Chris Lattner</a></address>
<!-- Created: Tue Jan 23 15:19:28 CST 2001 -->
<!-- hhmts start -->
-Last modified: Thu May 8 10:48:46 CDT 2003
+Last modified: Wed Jun 18 16:29:55 CDT 2003
<!-- hhmts end -->
</font>
</body></html>
Index: llvm/www/docs/OpenProjects.html
diff -u llvm/www/docs/OpenProjects.html:1.6 llvm/www/docs/OpenProjects.html:1.6.2.1
--- llvm/www/docs/OpenProjects.html:1.6 Tue May 6 15:47:11 2003
+++ llvm/www/docs/OpenProjects.html Thu Jun 26 16:36:22 2003
@@ -130,7 +130,6 @@
<li>Transform <tt>setjmp</tt> and <tt>longjmp</tt> calls to use the LLVM
<tt>invoke</tt> mechanism.
<li>Add support for a volatile attribute on loads and stores
-<li>Support for variable argument functions
<li>Add a new conditional move instruction: <tt>X = select bool Cond, Y, Z</tt>
<li>Add support for platform independent prefetch support. The GCC <a
href="http://gcc.gnu.org/projects/prefetch.html">prefetch project</a> page
@@ -192,7 +191,7 @@
<li>Implement a flow-sensitive context-sensitive alias analysis algorithm<br>
- Pick one of the somewhat efficient algorithms, but strive for maximum
precision
-<li>Implement a flow-sensitive context-insensitive alias anlaysis algorithm<br>
+<li>Implement a flow-sensitive context-insensitive alias analysis algorithm<br>
- Just an efficient local algorithm perhaps?
<li>Implement an interface to update analyses in response to common code motion
@@ -200,15 +199,6 @@
<li>Implement alias analysis based optimizations:
<ul>
<li>Dead store elimination
- <li>Store+Reload or "store forwarding" elimination:<p>
- Change:
- <pre>
- store int X, int* P
- Y = load int* P</pre>
- into:
- <pre>
- store int X, int *P
- Y = X</pre>
</ul>
</ol>
@@ -290,6 +280,6 @@
<address><a href="mailto:sabre at nondot.org">Chris Lattner</a></address>
<!-- Created: Tue Aug 6 15:00:33 CDT 2002 -->
<!-- hhmts start -->
-Last modified: Tue May 6 15:46:48 CDT 2003
+Last modified: Wed Jun 25 09:30:27 CDT 2003
<!-- hhmts end -->
</font></body></html>
More information about the llvm-commits
mailing list