Displaying 4 results from an estimated 4 matches for "dumpnodesr".
2009 Dec 18
2
[LLVMdev] [PATCH] dbgs() Use
...etRoot().getNode()) DumpNodes(getRoot().getNode(), 2, this);
- errs() << "\n\n";
+ dbgs() << "\n\n";
}
void SDNode::printr(raw_ostream &OS, const SelectionDAG *G) const {
@@ -6049,12 +6050,12 @@
void SDNode::dumpr() const {
VisitedSDNodeSet once;
- DumpNodesr(errs(), this, 0, 0, once);
+ DumpNodesr(dbgs(), this, 0, 0, once);
}
void SDNode::dumpr(const SelectionDAG *G) const {
VisitedSDNodeSet once;
- DumpNodesr(errs(), this, 0, G, once);
+ DumpNodesr(dbgs(), this, 0, G, once);
}
Index: lib/Target/X86/X86ISelDAGToDAG.cpp
==================...
2010 Jan 15
0
[LLVMdev] [PATCH] SelectionDAG Debugging
...recursion dumping is what the existing dump routines
> >> already do, so it's a little odd to have a flag to allow these
> >
> > Which existing dump routines are you referring to?
>
> dumpr(). I guess it wasn't commented. It is now :-).
Ah, one thing. dumpr uses DumpNodesr which does the "once" thing.
I actually would prefer a full dump. Perhaps we shouldn't try to
unify them, or maybe provide a flag to control behavior. In the
past separate APIs have been preferred over flags. I can rename
the ones I added to be more consistent with the existing stu...
2010 Jan 16
1
[LLVMdev] [PATCH] SelectionDAG Debugging
...existing dump routines
>>>> already do, so it's a little odd to have a flag to allow these
>>>
>>> Which existing dump routines are you referring to?
>>
>> dumpr(). I guess it wasn't commented. It is now :-).
>
> Ah, one thing. dumpr uses DumpNodesr which does the "once" thing.
> I actually would prefer a full dump. Perhaps we shouldn't try to
> unify them, or maybe provide a flag to control behavior. In the
> past separate APIs have been preferred over flags. I can rename
> the ones I added to be more consistent w...
2010 Jan 15
3
[LLVMdev] [PATCH] SelectionDAG Debugging
On Jan 15, 2010, at 1:38 PM, David Greene wrote:
> On Friday 15 January 2010 15:09, Dan Gohman wrote:
>
>>> Sound good? reimplement
>>
>> Unlimited-recursion dumping is what the existing dump routines
>> already do, so it's a little odd to have a flag to allow these
>
> Which existing dump routines are you referring to?
dumpr(). I guess it wasn't