Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-06-03 Thread Indu Bhagat
Hello, On 05/24/2019 06:24 AM, Jakub Jelinek wrote: On Tue, May 21, 2019 at 03:44:47PM -0700, Indu Bhagat wrote: Yes and No :) And that is indeed one of the motivation of the project - to allow CTF generation where it's most suited aka the toolchain. There do exist utilties for generation of

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-06-03 Thread Richard Biener
On Fri, May 31, 2019 at 9:17 PM Indu Bhagat wrote: > > > > On 05/24/2019 02:26 AM, Richard Biener wrote: > > Currently, it does look like CTF for possibly to-be-omitted symbols will be > generated... I assume even DWARF needs to handle this case. Can you point me > to > how DWARF does this ? > >

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-06-03 Thread Richard Biener
On Sat, Jun 1, 2019 at 2:14 AM Indu Bhagat wrote: > > > > On 05/29/2019 12:15 AM, Richard Biener wrote: > > Of course. We are merely discussing of where the triggering of processing > starts: debug hooks, or something like: > > dwarf2out_early_finish() { >... >if (ctf) > ctf_emit();

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-31 Thread Indu Bhagat
On 05/29/2019 12:15 AM, Richard Biener wrote: Of course. We are merely discussing of where the triggering of processing starts: debug hooks, or something like: dwarf2out_early_finish() { ... if (ctf) ctf_emit(); } (and then in addition if the current DWARF info would be the

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-31 Thread Indu Bhagat
On 05/24/2019 02:26 AM, Richard Biener wrote: Currently, it does look like CTF for possibly to-be-omitted symbols will be generated... I assume even DWARF needs to handle this case. Can you point me to how DWARF does this ? It emits the debug information. DWARF outputs a representation of

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-29 Thread Richard Biener
On Mon, May 27, 2019 at 8:12 PM Indu Bhagat wrote: > > Hi Michael, > > On 05/24/2019 06:04 AM, Michael Matz wrote: > > Hello, > > > > On Thu, 23 May 2019, Indu Bhagat wrote: > > > >>> OK. So I wonder how difficult it is to emit CTF by walking dwarf2outs own > >>> data structures? That is, in my

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-27 Thread Indu Bhagat
Hi Michael, On 05/24/2019 06:04 AM, Michael Matz wrote: Hello, On Thu, 23 May 2019, Indu Bhagat wrote: OK. So I wonder how difficult it is to emit CTF by walking dwarf2outs own data structures? That is, in my view CTF should be emitted by dwarf2out_early_finish () (which is also the point

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-24 Thread Jakub Jelinek
On Fri, May 24, 2019 at 03:24:34PM +0200, Jakub Jelinek wrote: > On Tue, May 21, 2019 at 03:44:47PM -0700, Indu Bhagat wrote: > > Yes and No :) And that is indeed one of the motivation of the project - to > > allow CTF generation where it's most suited aka the toolchain. > > > > There do exist

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-24 Thread Jakub Jelinek
On Tue, May 21, 2019 at 03:44:47PM -0700, Indu Bhagat wrote: > Yes and No :) And that is indeed one of the motivation of the project - to > allow CTF generation where it's most suited aka the toolchain. > > There do exist utilties for generation of CTF from DWARF. For example, one of > them is

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-24 Thread Michael Matz
Hello, On Thu, 23 May 2019, Indu Bhagat wrote: > > OK. So I wonder how difficult it is to emit CTF by walking dwarf2outs own > > data structures? That is, in my view CTF should be emitted by > > dwarf2out_early_finish () (which is also the point LTO type/decl debug > > is generated from). It

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-24 Thread Richard Biener
On Thu, May 23, 2019 at 10:31 PM Indu Bhagat wrote: > > > > On 05/22/2019 02:04 AM, Richard Biener wrote: > > The CTF debug information is kept in a CTF container distinct from the > frontend > structures. HashMaps are used to avoid generation of duplicate CTF and to > book-keep the generated

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-23 Thread Indu Bhagat
On 05/22/2019 02:04 AM, Richard Biener wrote: The CTF debug information is kept in a CTF container distinct from the frontend structures. HashMaps are used to avoid generation of duplicate CTF and to book-keep the generated CTF. OK. So I wonder how difficult it is to emit CTF by walking

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-22 Thread Richard Biener
On Wed, May 22, 2019 at 12:34 AM Indu Bhagat wrote: > > Thanks for your feedback. Comments inline. > > > On 05/21/2019 03:28 AM, Richard Biener wrote: > > GCC RFC patch set : > Patch 1 is a simple addition of a new function lang_GNU_GIMPLE to check for > GIMPLE frontend. > > I don't think you

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-21 Thread Indu Bhagat
Thanks for your feedback. Comments inline. On 05/21/2019 03:28 AM, Richard Biener wrote: GCC RFC patch set : Patch 1 is a simple addition of a new function lang_GNU_GIMPLE to check for GIMPLE frontend. I don't think you should need this - the GIMPLE "frontend" is intended for unit testing

Re: [PATCH,RFC 0/3] Support for CTF in GCC

2019-05-21 Thread Richard Biener
On Mon, May 20, 2019 at 7:56 PM Indu Bhagat wrote: > > Background : > CTF is the Compact Ansi-C Type Format. It is a format designed to express some > characteristics (specifically Type information) of the data types in a C > program. CTF format is compact and fast; It was originally designed for

[PATCH,RFC 0/3] Support for CTF in GCC

2019-05-20 Thread Indu Bhagat
Background : CTF is the Compact Ansi-C Type Format. It is a format designed to express some characteristics (specifically Type information) of the data types in a C program. CTF format is compact and fast; It was originally designed for use-cases like dynamic tracing, online in-application