From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>, Nix <nix@esperi.org.uk>
Cc: Richard Biener <richard.guenther@gmail.com>,
Indu Bhagat <indu.bhagat@oracle.com>,
Indu Bhagat <ibhagatgnu@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH,RFC,V3 0/5] Support for CTF in GCC
Date: Wed, 10 Jul 2019 00:50:00 -0000 [thread overview]
Message-ID: <abf36301-c859-cc88-1118-12035d17e4ce@redhat.com> (raw)
In-Reply-To: <20190709232514.GB14074@gate.crashing.org>
On 7/9/19 5:25 PM, Segher Boessenkool wrote:
> On Fri, Jul 05, 2019 at 07:28:12PM +0100, Nix wrote:
>> On 5 Jul 2019, Richard Biener said:
>>
>>> On Fri, Jul 5, 2019 at 12:21 AM Indu Bhagat <indu.bhagat@oracle.com> wrote:
>>>> CTF, at this time, is type information for entities at global or file scope.
>>>> This can be used by online debuggers, program tracers (dynamic tracing); More
>>>> generally, it provides type introspection for C programs, with an optional
>>>> library API to allow them to get at their own types quite more easily than
>>>> DWARF. So, the umbrella usecases are - all C programs that want to introspect
>>>> their own types quickly; and applications that want to introspect other
>>>> programs's types quickly.
>>>
>>> What makes it superior to DWARF stripped down to the above feature set?
>>
>> Increased compactness.
>
> Does CTF support something like -fasynchronous-unwind-tables? You need
> that to have any sane debugging on many platforms. Without it, you
> even have only partial backtraces, on most architectures/ABIs anyway.
I'd be suprised if it did since you need location information. FWIW,
low level libraries like glibc depend on this stuff to support cancellation.
jeff
next prev parent reply other threads:[~2019-07-10 0:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 6:37 Indu Bhagat
2019-06-27 6:37 ` [PATCH,RFC,V3 2/5] Add CTF command line options : -gtLEVEL Indu Bhagat
2019-06-27 6:37 ` [PATCH,RFC,V3 4/5] CTF generation for a single compilation unit Indu Bhagat
2019-06-27 6:37 ` [PATCH,RFC,V3 1/5] Add new function lang_GNU_GIMPLE Indu Bhagat
2019-06-27 6:37 ` [PATCH,RFC,V3 5/5] Update CTF testsuite Indu Bhagat
2019-06-27 6:37 ` [PATCH,RFC,V3 3/5] Setup for CTF generation and emission Indu Bhagat
2019-07-02 17:43 ` [PATCH,RFC,V3 0/5] Support for CTF in GCC Indu Bhagat
2019-07-03 3:18 ` Jeff Law
2019-07-03 12:39 ` Richard Biener
2019-07-04 1:49 ` Indu Bhagat
2019-07-04 10:47 ` Richard Biener
2019-07-04 22:44 ` Indu Bhagat
2019-07-05 11:25 ` Richard Biener
2019-07-05 18:28 ` Nix
2019-07-05 19:37 ` Jakub Jelinek
2019-07-08 14:16 ` Nix
2019-07-09 23:25 ` Mike Stump
2019-07-11 12:25 ` Nix
2019-07-09 23:46 ` Segher Boessenkool
2019-07-10 0:50 ` Jeff Law [this message]
2019-07-11 12:59 ` Nix
2019-07-11 16:54 ` Segher Boessenkool
2019-07-09 17:32 ` Indu Bhagat
2019-07-04 0:36 ` Indu Bhagat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abf36301-c859-cc88-1118-12035d17e4ce@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ibhagatgnu@gmail.com \
--cc=indu.bhagat@oracle.com \
--cc=nix@esperi.org.uk \
--cc=richard.guenther@gmail.com \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).