[cfe-commits] r167799 - /cfe/trunk/lib/Driver/Tools.cpp

[Eric Christopher]

> >
> > I talked with Greg and he said that accel tables wouldn't work with LTO.
> The problem is triggered even with `-gline-tables-only'. I don't have a
> small testcase, but you need to build LLVM with LTO and
> `-gline-tables-only' then run dwarfdump on it like I said.
> >
> >
> > That's curious, did he give a reason?
>
> I think it had to do with messed up debug info. Greg, could you explain a
> bit more?
>
>
Yeah. Curious here since if dsymutil can construct them we should be able
to as well.


> > You can have an accelerator table for a final executable. That said the
> accelerator tables make not sense for -gline-tables-only which could be
> causing you the problems you're see since there's very little info for the
> tables to work with and there could be issues there. There should be a DIE
> for each entry in the names table. What do, for example, those offsets give
> you?
> >
> The offsets are bogus. I can't find them in the dwarfdump.
>
>
OK. What's the assembly look like and what are the offsets for those names?


> > > Do you have a particular set of output from the verify to show what's
> going on here?
> > >
> > These are the first several lines of the verify output. It's big.
> >
> > Not surprising as it's pretty heinous debug info at this point. So, what
> are the DIE offsets for those functions? llvm-dwarfdump doesn't dump them
> at the moment so you'll need to use dwarfdump to look for the functions.
> >
> I'll take a look after lunch. I might be able to reduce a testcase to look
> at...
>

Cool.

-eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20121113/aa310b88/attachment.html>