public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 3826495d1a2c265954d5da13ca71925eea390060 Date: Mon, 13 Sep 2021 14:38:10 +0000 (GMT) [thread overview] Message-ID: <20210913143810.153473857416@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 3826495d1a2c265954d5da13ca71925eea390060 (commit) from 174d4dd6abf0c164f56a2149377979ed7eeeae1e (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 3826495d1a2c265954d5da13ca71925eea390060 Author: Jose E. Marchesi <jose.marchesi@oracle.com> Date: Fri Sep 10 15:44:30 2021 +0200 gcc-12/changes.html: BPF, CTF and BTF update * htdocs/gcc-12/changes.html (BPF): Item about the CO-RE support. (Debugging formats): New section with items about the support for CTF and BTF. diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 946faa49..936af979 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -143,6 +143,15 @@ a work-in-progress.</p> <!-- <h3 id="avr">AVR</h3> --> +<h3 id="bpf">BPF</h3> +<ul> + <li>Support for CO-RE (compile-once, run-everywhere) has been added + to the BPF backend. CO-RE allows to compile portable BPF + programs that are able to run among different versions of the + Linux kernel. + </li> +</ul> + <!-- <h3 id="x86">IA-32/x86-64</h3> --> <!-- <h3 id="mips">MIPS</h3> --> @@ -210,7 +219,25 @@ a work-in-progress.</p> <!-- <h2 id="plugins">Improvements for plugin authors</h2> --> <!-- .................................................................. --> -<!-- <h2>Other significant improvements</h2> --> +<h2>Other significant improvements</h2> + +<h3 id="debug">Debugging formats</h3> + +<ul> + <li>GCC can now generate debugging information + in <a href="https://ctfstd.org">CTF</a>, a lightweight debugging + format that provides information about C types and the + association between functions and data symbols and types. This + format is designed to be embedded in ELF files and to be very + compact and simple. A new command-line + option <code>-gctf</code> enables the generation of CTF. + </li> + <li>GCC can now generate debugging information in BTF. This is a + debugging format mainly used in BPF programs and the Linux + kernel. The compiler can generate BTF for any target, when + enabled with the command-line option <code>-gbtf</code> + </li> +</ul> <!-- .................................................................. --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-09-13 14:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210913143810.153473857416@sourceware.org \ --to=jemarch@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).