From 254aa7cf2b1176f39f9f293715cbc4a0873e0d9b Mon Sep 17 00:00:00 2001 From: Nick Lewycky Date: Wed, 18 Jul 2007 04:24:20 +0000 Subject: [PATCH] Alphabetize. Document -mlimit parameter. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@39990 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CommandGuide/bugpoint.pod | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/docs/CommandGuide/bugpoint.pod b/docs/CommandGuide/bugpoint.pod index d940f0d4291..12e32fbb2f5 100644 --- a/docs/CommandGuide/bugpoint.pod +++ b/docs/CommandGuide/bugpoint.pod @@ -64,6 +64,12 @@ program. By default, B uses these passes internally when attempting to reduce test programs. If you're trying to find a bug in one of these passes, B 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 + +Specifies an upper limit on memory usage of the optimization and codegen. Set +to zero to disable the limit. + =item B<--output> F 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 -- 2.34.1