On Thu, Jun 24, 2021 at 5:31 PM Jason Merrill via Gcc-patches
wrote:
>
> On 6/24/21 11:13 AM, Jose E. Marchesi wrote:
> >
> > This patch introduces a dwarf2int.h header, to be used by code that
> > needs access to the internal DIE structures and their attributes.
>
> Why not put
On 6/24/21 11:13 AM, Jose E. Marchesi wrote:
This patch introduces a dwarf2int.h header, to be used by code that
needs access to the internal DIE structures and their attributes.
Why not put these bits in dwarf2out.h?
We think that it makes sense to have a separated interface file for
the
im
This patch introduces a dwarf2int.h header, to be used by code that
needs access to the internal DIE structures and their attributes.
>>>
>>> Why not put these bits in dwarf2out.h?
>> We think that it makes sense to have a separated interface file for
>> the
>> implementation of DWARF-b
On 6/24/21 9:52 AM, Jose E. Marchesi wrote:
On 5/31/21 12:57 PM, Jose E. Marchesi via Gcc-patches wrote:
This patch introduces a dwarf2int.h header, to be used by code that
needs access to the internal DIE structures and their attributes.
Why not put these bits in dwarf2out.h?
We think that
Hi Jason.
> On 5/31/21 12:57 PM, Jose E. Marchesi via Gcc-patches wrote:
>> This patch introduces a dwarf2int.h header, to be used by code that
>> needs access to the internal DIE structures and their attributes.
>
> Why not put these bits in dwarf2out.h?
We think that it makes sense to have a
On 5/31/21 12:57 PM, Jose E. Marchesi via Gcc-patches wrote:
This patch introduces a dwarf2int.h header, to be used by code that
needs access to the internal DIE structures and their attributes.
Why not put these bits in dwarf2out.h?
The following functions which were previously defined as st
This patch introduces a dwarf2int.h header, to be used by code that
needs access to the internal DIE structures and their attributes.
The following functions which were previously defined as static in
dwarf2out.c are now non-static, and extern prototypes for them have
been added to dwarf2int.h:
-
