summaryrefslogtreecommitdiff
path: root/docs/CommandGuide
diff options
context:
space:
mode:
authorNick Lewycky <nicholas@mxc.ca>2007-07-18 04:24:20 +0000
committerNick Lewycky <nicholas@mxc.ca>2007-07-18 04:24:20 +0000
commit254aa7cf2b1176f39f9f293715cbc4a0873e0d9b (patch)
tree8ca82e7a427008b714ecf062f53c1cdd81f0742c /docs/CommandGuide
parentb63c7b695f14bc23b8491a609f99d8cfe1996aef (diff)
downloadllvm-254aa7cf2b1176f39f9f293715cbc4a0873e0d9b.tar.gz
llvm-254aa7cf2b1176f39f9f293715cbc4a0873e0d9b.tar.bz2
llvm-254aa7cf2b1176f39f9f293715cbc4a0873e0d9b.tar.xz
Alphabetize. Document -mlimit parameter.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@39990 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/CommandGuide')
-rw-r--r--docs/CommandGuide/bugpoint.pod17
1 files changed, 11 insertions, 6 deletions
diff --git a/docs/CommandGuide/bugpoint.pod b/docs/CommandGuide/bugpoint.pod
index d940f0d429..12e32fbb2f 100644
--- a/docs/CommandGuide/bugpoint.pod
+++ b/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