Hello,
this is the first time I am writing to a mailing list. I've tried
researching the normal procedure but nothing special seems to be required.
I'm currently trying to do a complete graph-discovery of GCC's symtab /
tree_nodes to dump the full internal representation of the compilation
unit.
On Sun, 25 Jun 2023 at 04:18, Jan Hubicka wrote:
> > Hi,
> Hi,
> I am sorry for late reaction.
>
No problem!
> > I am working on the GSOC project "Bypass Assembler when generating LTO
> > object files." So as a first step, I am adding .symtab along with
> > __gnu_lto_slim symbol into it so that
On Mon, Jun 26, 2023 at 10:01 AM Aaron Lorey via Gcc wrote:
>
> Hello,
>
> this is the first time I am writing to a mailing list. I've tried
> researching the normal procedure but nothing special seems to be required.
>
> I'm currently trying to do a complete graph-discovery of GCC's symtab /
> tr
> > > +simple_object_write_add_symbol(simple_object_write *sobj, const char
> > *name,
> > > +size_t size, unsigned int align);
> >
> > Symbols has much more properties in addition to sizes and alignments.
> > We will eventually need to get dwarf writting, so we will need to
> > support them. Howev
On Mon, 2023-06-26 at 18:59 +0200, Aaron Lorey via Gcc wrote:
> Hello,
>
> this is the first time I am writing to a mailing list. I've tried
> researching the normal procedure but nothing special seems to be
> required.
>
> I'm currently trying to do a complete graph-discovery of GCC's symtab
> /
On Mon, 26 Jun 2023 at 23:24, Jan Hubicka wrote:
> > > > +simple_object_write_add_symbol(simple_object_write *sobj, const char
> > > *name,
> > > > +size_t size, unsigned int align);
> > >
> > > Symbols has much more properties in addition to sizes and alignments.
> > > We will eventually need to
