diff options
Diffstat (limited to 'llvm/docs')
| -rw-r--r-- | llvm/docs/CommandLine.html | 2 | ||||
| -rw-r--r-- | llvm/docs/ProgrammersManual.html | 26 | ||||
| -rw-r--r-- | llvm/docs/WritingAnLLVMPass.html | 8 |
3 files changed, 18 insertions, 18 deletions
diff --git a/llvm/docs/CommandLine.html b/llvm/docs/CommandLine.html index b04820e88a5..8358d8756e1 100644 --- a/llvm/docs/CommandLine.html +++ b/llvm/docs/CommandLine.html @@ -1042,7 +1042,7 @@ extern bool DebugFlag; // debug build, then the code specified as the option to the macro will be // executed. Otherwise it will not be. Example: // -// DEBUG(std::cerr << "Bitset contains: " << Bitset << "\n"); +// DOUT << "Bitset contains: " << Bitset << "\n"; //</i> <span class="doc_hilite">#ifdef NDEBUG #define DEBUG(X) diff --git a/llvm/docs/ProgrammersManual.html b/llvm/docs/ProgrammersManual.html index 950c937824a..4fd3a4a5e59 100644 --- a/llvm/docs/ProgrammersManual.html +++ b/llvm/docs/ProgrammersManual.html @@ -395,7 +395,7 @@ tool) is run with the '<tt>-debug</tt>' command line argument:</p> <div class="doc_code"> <pre> -DEBUG(std::cerr << "I am here!\n"); +DOUT << "I am here!\n"; </pre> </div> @@ -440,16 +440,16 @@ option as follows:</p> <div class="doc_code"> <pre> -DEBUG(std::cerr << "No debug type\n"); +DOUT << "No debug type\n"; #undef DEBUG_TYPE #define DEBUG_TYPE "foo" -DEBUG(std::cerr << "'foo' debug type\n"); +DOUT << "'foo' debug type\n"; #undef DEBUG_TYPE #define DEBUG_TYPE "bar" -DEBUG(std::cerr << "'bar' debug type\n"); +DOUT << "'bar' debug type\n"; #undef DEBUG_TYPE #define DEBUG_TYPE "" -DEBUG(std::cerr << "No debug type (2)\n"); +DOUT << "No debug type (2)\n"; </pre> </div> @@ -695,8 +695,8 @@ an example that prints the name of a <tt>BasicBlock</tt> and the number of for (Function::iterator i = func->begin(), e = func->end(); i != e; ++i) // <i>Print out the name of the basic block if it has one, and then the</i> // <i>number of instructions that it contains</i> - std::cerr << "Basic block (name=" << i->getName() << ") has " - << i->size() << " instructions.\n"; + llvm::cerr << "Basic block (name=" << i->getName() << ") has " + << i->size() << " instructions.\n"; </pre> </div> @@ -728,14 +728,14 @@ a <tt>BasicBlock</tt>:</p> for (BasicBlock::iterator i = blk->begin(), e = blk->end(); i != e; ++i) // <i>The next statement works since operator<<(ostream&,...)</i> // <i>is overloaded for Instruction&</i> - std::cerr << *i << "\n"; + llvm::cerr << *i << "\n"; </pre> </div> <p>However, this isn't really the best way to print out the contents of a <tt>BasicBlock</tt>! Since the ostream operators are overloaded for virtually anything you'll care about, you could have just invoked the print routine on the -basic block itself: <tt>std::cerr << *blk << "\n";</tt>.</p> +basic block itself: <tt>llvm::cerr << *blk << "\n";</tt>.</p> </div> @@ -761,7 +761,7 @@ small example that shows how to dump all instructions in a function to the stand // <i>F is a ptr to a Function instance</i> for (inst_iterator i = inst_begin(F), e = inst_end(F); i != e; ++i) - std::cerr << *i << "\n"; + llvm::cerr << *i << "\n"; </pre> </div> @@ -837,7 +837,7 @@ without actually obtaining it via iteration over some structure:</p> void printNextInstruction(Instruction* inst) { BasicBlock::iterator it(inst); ++it; // <i>After this line, it refers to the instruction after *inst</i> - if (it != inst->getParent()->end()) std::cerr << *it << "\n"; + if (it != inst->getParent()->end()) llvm::cerr << *it << "\n"; } </pre> </div> @@ -956,8 +956,8 @@ Function* F = ...; for (Value::use_iterator i = F->use_begin(), e = F->use_end(); i != e; ++i) if (Instruction *Inst = dyn_cast<Instruction>(*i)) { - std::cerr << "F is used in instruction:\n"; - std::cerr << *Inst << "\n"; + llvm::cerr << "F is used in instruction:\n"; + llvm::cerr << *Inst << "\n"; } </pre> </div> diff --git a/llvm/docs/WritingAnLLVMPass.html b/llvm/docs/WritingAnLLVMPass.html index b33edb0eb68..0c362d0e7c6 100644 --- a/llvm/docs/WritingAnLLVMPass.html +++ b/llvm/docs/WritingAnLLVMPass.html @@ -257,7 +257,7 @@ time.</p> <div class="doc_code"><pre> <b>virtual bool</b> <a href="#runOnFunction">runOnFunction</a>(Function &F) { - std::cerr << "<i>Hello: </i>" << F.getName() << "\n"; + llvm::cerr << "<i>Hello: </i>" << F.getName() << "\n"; <b>return false</b>; } }; <i>// end of struct Hello</i> @@ -289,7 +289,7 @@ argument "<tt>hello</tt>", and a name "<tt>Hello World Pass</tt>".</p> <b>namespace</b> { <b>struct Hello</b> : <b>public</b> <a href="#FunctionPass">FunctionPass</a> { <b>virtual bool</b> <a href="#runOnFunction">runOnFunction</a>(Function &F) { - std::cerr << "<i>Hello: </i>" << F.getName() << "\n"; + llvm::cerr << "<i>Hello: </i>" << F.getName() << "\n"; <b>return false</b>; } }; @@ -863,7 +863,7 @@ implement the virtual <tt>print</tt> method:</p> <div class="doc_text"> <div class="doc_code"><pre> - <b>virtual void</b> print(std::ostream &O, <b>const</b> Module *M) <b>const</b>; + <b>virtual void</b> print(llvm::OStream &O, <b>const</b> Module *M) <b>const</b>; </pre></div> <p>The <tt>print</tt> method must be implemented by "analyses" in order to print @@ -871,7 +871,7 @@ a human readable version of the analysis results. This is useful for debugging an analysis itself, as well as for other people to figure out how an analysis works. Use the <tt>opt -analyze</tt> argument to invoke this method.</p> -<p>The <tt>ostream</tt> parameter specifies the stream to write the results on, +<p>The <tt>llvm::OStream</tt> parameter specifies the stream to write the results on, and the <tt>Module</tt> parameter gives a pointer to the top level module of the program that has been analyzed. Note however that this pointer may be null in certain circumstances (such as calling the <tt>Pass::dump()</tt> from a |
