Alphabetize. Document -mlimit parameter.

llvm-svn: 39990

1 files changed, 11 insertions, 6 deletions

diff --git a/llvm/docs/CommandGuide/bugpoint.pod b/llvm/docs/CommandGuide/bugpoint.pod
index d940f0d4291..12e32fbb2f5 100644
--- a/llvm/docs/CommandGuide/bugpoint.pod
+++ b/llvm/docs/CommandGuide/bugpoint.pod
@@ -64,6 +64,12 @@ program. By default, B<bugpoint> uses these passes internally when attempting to
 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 @@ optimizations, use the B<--help> and B<--load> options together; for example:
 
     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 @@ using the specified code generator.  These options allow you to choose the
 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