This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Yet another tree dumper : Part 2 (4/4)
Mark Mitchell wrote:
There is no reason to have two tree dumpers. If the new one is better,
let's use it. If it's not better, then Devang should work on it until
it is. The last thing we need is more superfluous code in GCC.
There appears to be consenus on this point. But it might be useful
during a transition period to have both of them in there. If the
new dumper isn't emitting some needed information, do:
set use_new_dumper=1
continue debugging, and then submit a bug report.
After a month or so with no major complaints about the
new dumper, rip the old one out.
However, I don't feel strongly about this issue. If there is some
particular missing information in the new dumper's output, then one
can always uses gdb's print command directly until the new dumper
is improved.
--
--Per Bothner
per@bothner.com http://per.bothner.com/