[Bug debug/91239] gcc generates invalid .debug_macro sections (according to lld folks)

rguenth at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Wed Jul 24 08:07:00 GMT 2019


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91239

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2019-07-24
                 CC|                            |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
So how does a testcase look like?  If I read the code in dwarf2out correctly
the only way things could go wrong is a hash collision, otherwise I don't
see how the comdat sections could differ.

Can you possibly share two source files and instructions to reproduce the
conflicting comdats?

There should be also only a single symbol at the start of the comdat so
the relocation should be always resolvable.  Maybe we're somehow emitting
the same info twice into the same comdat from a single CU?

That said, w/o an object file to look at it's hard to say what's wrong.


More information about the Gcc-bugs mailing list