[llvm-commits] CVS: llvm/docs/CommandGuide/analyze.html bugpoint.html gccld.html opt.html

Mon Jan 26 15:28:02 PST 2004

Changes in directory llvm/docs/CommandGuide:

analyze.html updated: 1.8 -> 1.9
bugpoint.html updated: 1.19 -> 1.20
gccld.html updated: 1.8 -> 1.9
opt.html updated: 1.8 -> 1.9

---
Log message:

Clarified the extension to shared library objects.



---
Diffs of the changes:  (+30 -19)

Index: llvm/docs/CommandGuide/analyze.html
diff -u llvm/docs/CommandGuide/analyze.html:1.8 llvm/docs/CommandGuide/analyze.html:1.9

--- llvm/docs/CommandGuide/analyze.html:1.8	Tue Oct  7 15:36:00 2003
+++ llvm/docs/CommandGuide/analyze.html	Mon Jan 26 15:26:54 2004
@@ -51,16 +51,16 @@
 	Quiet mode.  With this option, analysis pass names are not printed.
 	<p>
 
-	<li> -load <plugin.so>
+	<li> -load <plugin>
 	<br>
-	Load the specified dynamic object with name plugin.so.  This file
+	Load the specified dynamic object with name <tt>plugin</tt>.  This file
 	should contain additional analysis passes that register themselves with
 	the <tt>analyze</tt> program after being loaded.
 	<p>
 
 	After being loaded, additional command line options are made available
-	for running the passes made available by plugin.so.  Use
-	'<tt><tt>analyze</tt> -load <plugin.so> -help</tt>' to see the new
+	for running the passes made available by <tt>plugin</tt>.  Use
+	'<tt><tt>analyze</tt> -load <plugin> -help</tt>' to see the new
 	list of available analysis passes.
 	<p>
 </ul>


Index: llvm/docs/CommandGuide/bugpoint.html
diff -u llvm/docs/CommandGuide/bugpoint.html:1.19 llvm/docs/CommandGuide/bugpoint.html:1.20
--- llvm/docs/CommandGuide/bugpoint.html:1.19	Wed Nov  5 15:46:13 2003
+++ llvm/docs/CommandGuide/bugpoint.html	Mon Jan 26 15:26:54 2004
@@ -158,8 +158,8 @@
 <h3>OPTIONS</h3>
 
 <ul>
-	<li><tt>-additional-so <library.so></tt><br>
-    Load <tt><library.so></tt> into the test program whenever it is run.
+	<li><tt>-additional-so <library></tt><br>
+    Load <tt><library></tt> into the test program whenever it is run.
     This is useful if you are debugging programs which depend on non-LLVM
     libraries (such as the X or curses libraries) to run.<p>
 
@@ -189,14 +189,14 @@
     test program, whenever it runs, to come from that file.
 	<p>
 
-	<a name="opt_load"><li> <tt>-load <plugin.so></tt><br>
-	Load the dynamic object <tt><plugin.so></tt> into <tt>bugpoint</tt>
+	<a name="opt_load"><li> <tt>-load <plugin></tt><br>
+	Load the dynamic object <tt><plugin></tt> into <tt>bugpoint</tt>
     itself.  This object should register new
 	optimization passes.  Once loaded, the object will add new command line
 	options to enable various optimizations.  To see the new complete list
 	of optimizations, use the -help and -load options together:
 	<p>
-	<tt>bugpoint -load <plugin.so> -help</tt>
+	<tt>bugpoint -load <plugin> -help</tt>
 	<p>
 
 	<a name="opt_output"><li><tt>-output <filename></tt><br>


Index: llvm/docs/CommandGuide/gccld.html
diff -u llvm/docs/CommandGuide/gccld.html:1.8 llvm/docs/CommandGuide/gccld.html:1.9
--- llvm/docs/CommandGuide/gccld.html:1.8	Sun Nov 16 17:39:11 2003
+++ llvm/docs/CommandGuide/gccld.html	Mon Jan 26 15:26:54 2004
@@ -32,24 +32,35 @@
 
 <h4>Search Order</h4>
 
+<p>
 When looking for objects specified on the command line, <tt>gccld</tt> will
 search for the object first in the current directory and then in the directory
 specified by the <tt>LLVM_LIB_SEARCH_PATH</tt> environment variable.  If it
 cannot find the object, it fails.
-<p>
+</p>
 
+<p>
 When looking for a library specified with the -l option, <tt>gccld</tt> first
 attempts to load a file with that name from the current directory.  If that
 fails, it looks for lib<library>.bc, lib<library>.a, or
-lib<library>.so, in that order, in each directory added to the library
-search path with the -L option.  These directories are searched in order they
+lib<library>.<shared library extension>, in that order, in each
+directory added to the library search path with the -L option.  These
+directories are searched in the order they
 were specified.  If the library cannot be located, then <tt>gccld</tt> looks in
 the directory specified by the <tt>LLVM_LIB_SEARCH_PATH</tt> environment
-variable.  If it does not find lib<library>.[bc | a | so] there, it fails.
+variable.  If it does not find a library there, it fails.
+</p>
 
+<p>
+The shared library extension is usually <tt>.so</tt>, but it may differ
+depending upon the system.
+</p>
+
+<p>
 The -L option is global.  It does not matter where it is specified in the list
 of command line arguments; the directory is simply added to the search path and
 is applied to all libraries, preceding or succeeding, in the command line.
+</p>
 
 <h4>Link order</h4>
 
@@ -131,9 +142,9 @@
 	<br>
 	Specify libraries to include when linking the output file.  When
 	linking, <tt>gccld</tt> will first attempt to load a file with the
-	pathname library.  If that fails, it will then attempt to load
-	lib<library>.bc, lib<library>.a, and lib<library>.so,
-	in that order.
+	pathname <tt>library</tt>.  If that fails, it will then attempt to load
+	lib<library>.bc, lib<library>.a, and
+  lib<library>.<shared library extension>, in that order.
 	<p>
 
 	<li> -link-as-library


Index: llvm/docs/CommandGuide/opt.html
diff -u llvm/docs/CommandGuide/opt.html:1.8 llvm/docs/CommandGuide/opt.html:1.9
--- llvm/docs/CommandGuide/opt.html:1.8	Sun Oct 19 13:08:57 2003
+++ llvm/docs/CommandGuide/opt.html	Mon Jan 26 15:26:54 2004
@@ -88,14 +88,14 @@
 	Quiet mode.  Do not print messages on whether the program was modified.
 	<p>
 
-	<li> -load <plugin.so>
+	<li> -load <plugin>
 	<br>
-	Load the dynamic object <plugin.so>.  This object should register new
+	Load the dynamic object <plugin>.  This object should register new
 	optimization passes.  Once loaded, the object will add new command line
 	options to enable various optimizations.  To see the new complete list
 	of optimizations, use the -help and -load options together:
 	<p>
-	<tt>opt -load  <plugin.so> -help</tt>
+	<tt>opt -load  <plugin> -help</tt>
 	<p>
 
 	<li> -p



