[llvm-commits] [llvm] r39990 - /llvm/trunk/docs/CommandGuide/bugpoint.pod

[Nick Lewycky]

Author: nicholas
Date: Tue Jul 17 23:24:20 2007
New Revision: 39990

URL: http://llvm.org/viewvc/llvm-project?rev=39990&view=rev
Log:
Alphabetize. Document -mlimit parameter.

Modified:
    llvm/trunk/docs/CommandGuide/bugpoint.pod

Modified: llvm/trunk/docs/CommandGuide/bugpoint.pod
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/CommandGuide/bugpoint.pod?rev=39990&r1=39989&r2=39990&view=diff

==============================================================================
--- llvm/trunk/docs/CommandGuide/bugpoint.pod (original)
+++ llvm/trunk/docs/CommandGuide/bugpoint.pod Tue Jul 17 23:24:20 2007
@@ -64,6 +64,12 @@
 reduce test programs.  If you're trying to find a bug in one of these passes,
 B<bugpoint> may crash.
 
+=item B<--enable-valgrind>
+
+Use valgrind to find faults in the optimization phase. This will allow
+bugpoint to find otherwise asymptomatic problems caused by memory
+mis-management.
+
 =item B<-find-bugs>
 
 Continually randomize the specified passes and run them on the test program
@@ -87,6 +93,11 @@
 
     bugpoint --load myNewPass.so --help
 
+=item B<--mlimit> F<megabytes>
+
+Specifies an upper limit on memory usage of the optimization and codegen. Set
+to zero to disable the limit.
+
 =item B<--output> F<filename>
 
 Whenever the test program produces output on its standard output stream, it
@@ -105,12 +116,6 @@
 interpreter, the JIT compiler, the static native code compiler, or the C
 backend, respectively.
 
-=item B<--enable-valgrind>
-
-Use valgrind to find faults in the optimization phase. This will allow
-bugpoint to find otherwise asymptomatic problems caused by memory
-mis-management.
-
 =back
 
 =head1 EXIT STATUS