2012/4/10 Dave Korn <dave.korn.cyg...@gmail.com>: > On 10/04/2012 17:41, Paweł Sikora wrote: >> On Tuesday 10 of April 2012 10:46:14 Jakub Jelinek wrote: >>> On Mon, Apr 09, 2012 at 04:34:32PM -0700, Xinliang David Li wrote: >>>> Class hierarchy is one such feature that is useful. Assuming we have >>>> two hierarchies for gcc: one for values rooted at ValExp, and one for >>>> gimple stmts rooted at GimpInst. >>>> >>>> 1) For IR browsing, *) all the macro accessors can be eliminated -- a >>>> big plus for debugging; >>> Not that clear, if all the macros are replaced by tons of inline >>> functions, the debugging experience can be actually significantly worse. >> >> debugabilty can be improved with set of gdb python pretty printers which >> could present gcc's structures in human readable form (instead of union >> mix). >> > > Would that be much different from "call debug_tree(x)" which we already have?
Not really, but it would be easier to customize. I would like to see less debug_* routines in favor of some gdb python code. Heh, maybe we could even use the (non-existant) new plugin introspection API for that! Richard. > cheers, > DaveK >
