This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: objdump for gimple [lto]
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Paulo Matos <pmatos at broadcom dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 24 Jun 2013 14:36:00 +0200
- Subject: Re: objdump for gimple [lto]
- References: <19EB96622A777C4AB91610E763265F46208481 at SJEXCHMB14 dot corp dot ad dot broadcom dot com>
On Mon, Jun 24, 2013 at 1:20 PM, Paulo Matos <pmatos@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
>
>