6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-14 11:32:34 +00:00
Code Issues Projects Releases Wiki Activity

Clean up documentation and naming of variables.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@14119 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Reid Spencer 2004-06-10 18:38:44 +00:00
parent 236b7e2142
commit 23d46e70b1
1 changed files with 15 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
tools/llvm-abcd/llvm-abcd.cpp
View File

@ -2,7 +2,7 @@
// //
// The LLVM Compiler Infrastructure // The LLVM Compiler Infrastructure
// //
// This file was developed by Reid Spencerearch and is distributed under the // This file was developed by Reid Spencer and is distributed under the
// University of Illinois Open Source License. See LICENSE.TXT for details. // University of Illinois Open Source License. See LICENSE.TXT for details.
// //
//===----------------------------------------------------------------------===// //===----------------------------------------------------------------------===//
@ -13,17 +13,20 @@
// //
// Options: // Options:
// --help - Output information about command line switches // --help - Output information about command line switches
// --details - Provide detailed analysis of individual functions // --nodetails - Don't print out detailed informaton about individual
// --dump - Dump bytecode in readable format // blocks and functions
// --dump - Dump low-level bytecode structure in readable format
// //
// This tool provides analytical information about a bytecode file. It is // This tool provides analytical information about a bytecode file. It is
// intended as an aid to developers of bytecode reading and writing software. It // intended as an aid to developers of bytecode reading and writing software. It
// produces on std::out a summary of the bytecode file that shows various // produces on std::out a summary of the bytecode file that shows various
// statistics about the contents of the file. If the -details option is given // statistics about the contents of the file. By default this information is
// then the output includes detailed information about each function in the // detailed and contains information about individual bytecode blocks and the
// bytecode file. The tool is also able to print a bytecode file in a straight // functions in the module. To avoid this more detailed output, use the
// forward text format // that shows the containment and relationships of the // -nodetails option to limit the output to just module level information.
// information in the bytecode file (-dump option). // The tool is also able to print a bytecode file in a straight forward text
// format that shows the containment and relationships of the information in
// the bytecode file (-dump option).
//===----------------------------------------------------------------------===// //===----------------------------------------------------------------------===//
#include "llvm/Bytecode/Analyzer.h" #include "llvm/Bytecode/Analyzer.h"
@ -37,7 +40,7 @@ using namespace llvm;
static cl::opt<std::string> static cl::opt<std::string>
InputFilename(cl::Positional, cl::desc("<input bytecode>"), cl::init("-")); InputFilename(cl::Positional, cl::desc("<input bytecode>"), cl::init("-"));
static cl::opt<bool> Detailed ("nodetails", cl::desc("Skip detailed output")); static cl::opt<bool> NoDetails ("nodetails", cl::desc("Skip detailed output"));
static cl::opt<bool> Dump ("dump", cl::desc("Detailed output")); static cl::opt<bool> Dump ("dump", cl::desc("Detailed output"));
int int
@ -55,7 +58,7 @@ main(int argc, char **argv)
/// Determine what to generate /// Determine what to generate
bca.dumpBytecode = Dump; bca.dumpBytecode = Dump;
bca.detailedResults = !Detailed; bca.detailedResults = !NoDetails;
/// Analyze the bytecode file /// Analyze the bytecode file
AnalyzeBytecodeFile(InputFilename, bca, &ErrorMessage); AnalyzeBytecodeFile(InputFilename, bca, &ErrorMessage);