On Mon, Jun 24, 2013 at 1:20 PM, Paulo Matos <pma...@broadcom.com> wrote: > Hello, > > I see this item in http://gcc.gnu.org/wiki/LinkTimeOptimization : > 7. Browsing/dumping tools for LTO files > > Is there anything already out there, even if half-baked?
Nothing. > I am having trouble understanding a problem in LTO and I think the bug is in > the writing of trees into the object file but can't find a way to know this > unless I have something like an objdump for gimple. > > If there's no tool out there to straightforwardly know this, what's the best > approach to find out if there's a problem written in the LTO stream? Well, pinpoint the issue in the LTRANS unit (or use -flto-partition=none and pinpoint the issue in the WPA phase). You can then debug from creation of the bogus tree node / gimple stmt by breaking on ggc_internal_alloc_stat return statement conditional on the address of the bogus tree / gimple. Richard. > Cheers, > > Paulo Matos > >