Looks probably like a bug in GCC and best discussed in their forum? (clang
seems to produce the macro in the macinfo if you compile with
`-fdebug-macro` (& you have to put some emitted entity (like a function
definition) in the file before Clang will produce any debug info for the
file))
On Wed, S
On Thu, Sep 12, 2024 at 10:52:33AM -0700, David Blaikie via Dwarf-discuss wrote:
> Looks probably like a bug in GCC and best discussed in their forum? (clang
> seems to produce the macro in the macinfo if you compile with
> `-fdebug-macro` (& you have to put some emitted entity (like a function
> d
On Thu, Sep 12, 2024 at 11:08 AM Jakub Jelinek wrote:
> On Thu, Sep 12, 2024 at 10:52:33AM -0700, David Blaikie via Dwarf-discuss
> wrote:
> > Looks probably like a bug in GCC and best discussed in their forum?
> (clang
> > seems to produce the macro in the macinfo if you compile with
> > `-fdebu
Thanks so much for the detailed explanation. So clearly all the macros are
there as we can see from readelf. I ran it myself and can see all the
macros as David pointed out. And just to make sure I understand, this is
what I took away:
1. All the macros are in the file as we can see from readelf o
On Thu, Sep 12, 2024 at 05:10:01PM -0500, Lorenzo Gomez wrote:
> Thanks so much for the detailed explanation. So clearly all the macros are
> there as we can see from readelf. I ran it myself and can see all the
> macros as David pointed out. And just to make sure I understand, this is
> what I too
