public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: gcc-patches@gcc.gnu.org
Subject: [[PATCH V9] 5/7] CTF/BTF documentation
Date: Mon, 31 May 2021 18:58:00 +0200	[thread overview]
Message-ID: <20210531165802.5686-6-jose.marchesi@oracle.com> (raw)
In-Reply-To: <20210531165802.5686-1-jose.marchesi@oracle.com>

This commit documents the new command line options introduced by the
CTF and BTF debug formats.

2021-05-14  Indu Bhagat  <indu.bhagat@oracle.com>

	* doc/invoke.texi: Document the CTF and BTF debug info options.
---
 gcc/doc/invoke.texi | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 5cd4e2d993c..25dd50738de 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -466,6 +466,7 @@ Objective-C and Objective-C++ Dialects}.
 @item Debugging Options
 @xref{Debugging Options,,Options for Debugging Your Program}.
 @gccoptlist{-g  -g@var{level}  -gdwarf  -gdwarf-@var{version} @gol
+-gbtf -gctf  -gctf@var{level} @gol
 -ggdb  -grecord-gcc-switches  -gno-record-gcc-switches @gol
 -gstabs  -gstabs+  -gstrict-dwarf  -gno-strict-dwarf @gol
 -gas-loc-support  -gno-as-loc-support @gol
@@ -9696,6 +9697,25 @@ other DWARF-related options such as
 @option{-fno-dwarf2-cfi-asm}) retain a reference to DWARF Version 2
 in their names, but apply to all currently-supported versions of DWARF.
 
+@item -gbtf
+@opindex gbtf
+Request BTF debug information.
+
+@item -gctf
+@itemx -gctf@var{level}
+@opindex gctf
+Request CTF debug information and use level to specify how much CTF debug
+information should be produced.  If -gctf is specified without a value for
+level, the default level of CTF debug information is 2.
+
+Level 0 produces no CTF debug information at all.  Thus, -gctf0 negates -gctf.
+
+Level 1 produces CTF information for tracebacks only.  This includes callsite
+information, but does not include type information.
+
+Level 2 produces type information for entities (functions, data objects etc.)
+at file-scope or global-scope only.
+
 @item -gstabs
 @opindex gstabs
 Produce debugging information in stabs format (if that is supported),
-- 
2.25.0.2.g232378479e


  parent reply	other threads:[~2021-05-31 16:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 16:57 [[PATCH V9] 0/7] Support for the CTF and BTF debug formats Jose E. Marchesi
2021-05-31 16:57 ` [[PATCH V9] 1/7] dwarf: add a dwarf2int.h internal interface Jose E. Marchesi
2021-06-22 20:05   ` Jason Merrill
2021-06-24 13:52     ` Jose E. Marchesi
2021-06-24 14:41       ` Jason Merrill
2021-06-24 15:13         ` Jose E. Marchesi
2021-06-24 15:30           ` Jason Merrill
2021-06-25  7:47             ` Richard Biener
2021-05-31 16:57 ` [[PATCH V9] 2/7] dejagnu: modularize gcc-dg-debug-runtest a bit Jose E. Marchesi
2021-06-21 13:47   ` Richard Biener
2021-05-31 16:57 ` [[PATCH V9] 3/7] CTF/BTF debug formats Jose E. Marchesi
2021-06-21 14:10   ` Richard Biener
2021-06-21 15:33     ` Jose E. Marchesi
2021-06-22 20:21   ` Jason Merrill
2021-05-31 16:57 ` [[PATCH V9] 4/7] CTF/BTF testsuites Jose E. Marchesi
2021-06-21 14:02   ` Richard Biener
2021-05-31 16:58 ` Jose E. Marchesi [this message]
2021-06-21 13:51   ` [[PATCH V9] 5/7] CTF/BTF documentation Richard Biener
2021-05-31 16:58 ` [[PATCH V9] 6/7] Enable BTF generation in the BPF backend Jose E. Marchesi
2021-06-21 13:53   ` Richard Biener
2021-05-31 16:58 ` [[PATCH V9] 7/7] libiberty: copy over .BTF section when using LTO Jose E. Marchesi
2021-06-21 13:53   ` Richard Biener
2021-06-14 15:25 ` [[PATCH V9] 0/7] Support for the CTF and BTF debug formats Jose E. Marchesi
2021-06-21 14:01 ` Richard Biener
2021-06-22 15:30   ` Indu Bhagat
2021-06-22 20:22   ` Jason Merrill

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=20210531165802.5686-6-jose.marchesi@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=gcc-patches@gcc.gnu.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).