| John Criswell | 58ebcd0 | 2003-09-17 14:11:24 +0000 | [diff] [blame] | 1 | <html> |
| 2 | <title> |
| Chris Lattner | ee43b69 | 2003-09-25 19:50:05 +0000 | [diff] [blame^] | 3 | LLVM: extract tool |
| John Criswell | 58ebcd0 | 2003-09-17 14:11:24 +0000 | [diff] [blame] | 4 | </title> |
| 5 | |
| 6 | <body> |
| 7 | |
| 8 | <center> |
| Chris Lattner | ee43b69 | 2003-09-25 19:50:05 +0000 | [diff] [blame^] | 9 | <h1>LLVM: extract tool</h1> |
| John Criswell | 58ebcd0 | 2003-09-17 14:11:24 +0000 | [diff] [blame] | 10 | </center> |
| 11 | <HR> |
| 12 | |
| 13 | <h3> |
| 14 | NAME |
| 15 | </h3> |
| 16 | |
| 17 | extract |
| 18 | |
| 19 | <h3> |
| 20 | SYNOPSIS |
| 21 | </h3> |
| 22 | |
| 23 | extract [options] <filename> [filename ...] |
| 24 | <h3> |
| 25 | DESCRIPTION |
| 26 | </h3> |
| 27 | |
| 28 | The extract command takes the name of a function and extracts it from the |
| 29 | specified LLVM bytecode file. It is primarily used as a debugging tool to |
| 30 | reduce test cases from larger programs that are triggering a bug. |
| 31 | |
| 32 | <h3> |
| 33 | OPTIONS |
| 34 | </h3> |
| 35 | |
| 36 | <ul> |
| 37 | <li>-func <function> |
| 38 | <br> |
| 39 | Extract function from the LLVM bytecode. |
| 40 | <p> |
| 41 | |
| 42 | <li> -help |
| 43 | <br> |
| 44 | Print a summary of command line options. |
| 45 | <p> |
| 46 | |
| 47 | <li> -stats |
| 48 | <br> |
| 49 | Print statistics. |
| 50 | <p> |
| 51 | |
| 52 | <li> -time-passes |
| 53 | <br> |
| 54 | Record the amount of time needed for each pass and print it to standard |
| 55 | error. |
| 56 | </ul> |
| 57 | |
| 58 | <h3> |
| 59 | EXIT STATUS |
| 60 | </h3> |
| 61 | |
| 62 | If extract succeeds, it will exit with 0. Otherwise, if an error occurs, it |
| 63 | will exit with a non-zero value. |
| 64 | |
| 65 | <h3> |
| 66 | SEE ALSO |
| 67 | </h3> |
| 68 | bugpoint |
| 69 | |
| 70 | <HR> |
| 71 | <a href="http://llvm.cs.uiuc.edu">LLVM Team</a> |
| 72 | </body> |
| 73 | </html> |
| 74 | |