From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>,
Richard Biener <rguenther@suse.de>,
Kees Cook <keescook@chromium.org>
Subject: Re: [COMMITTED][patch][version 9]add -ftrivial-auto-var-init and variable attribute "uninitialized" to gcc
Date: Mon, 13 Sep 2021 16:38:24 +0200 [thread overview]
Message-ID: <87ee9sa6cf.fsf@oracle.com> (raw)
In-Reply-To: <CAFiYyc1n4QEGYZktiPncdmN67_KcBXgpXsxpgOD5S1a_1ngyQQ@mail.gmail.com> (Richard Biener's message of "Mon, 13 Sep 2021 11:32:20 +0200")
> On Fri, Sep 10, 2021 at 3:47 PM Jose E. Marchesi via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>>
>>
>> Hi Richard.
>>
>> > On Thu, 9 Sep 2021, Kees Cook wrote:
>> >
>> >> On Thu, Sep 09, 2021 at 10:49:11PM +0000, Qing Zhao wrote:
>> >> > Hi, FYI
>> >> >
>> >> > I just committed the following patch to gcc upstream:
>> >> >
>> >> >
>> >> > https://gcc.gnu.org/pipermail/gcc-cvs/2021-September/353195.html
>> >>
>> >> Hurray! Thank you so much for working on this, and thanks also to the
>> >> reviewers and everyone else poking at it.
>> >>
>> >> I will go update my Linux Plumbers slides to say "supported" instead of
>> >> "proposed". :)
>> >
>> > Can you two work on wording to add to gcc-12/changes.html for this
>> > feature? I think it deserves a release note. Likewise the CTF/BTF
>> > support btw.
>>
>> What about something like this for the BPF, CTF and BTF changes..
>
> Looks good to me!
Installed. Thanks!
> Thanks,
> Richard.
>
>> commit 3826495d1a2c265954d5da13ca71925eea390060 (HEAD -> master)
>> 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>
>>
>>
>> <!-- .................................................................. -->
next prev parent reply other threads:[~2021-09-13 14:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 20:07 [patch][version 8]add " Qing Zhao
2021-09-03 14:47 ` Qing Zhao
2021-09-11 8:03 ` [PATCH] testsuite: Fix c-c++-common/auto-init-* tests Jakub Jelinek
2021-09-11 11:45 ` Richard Biener
2021-09-11 16:58 ` Qing Zhao
2021-09-15 17:59 ` Qing Zhao
2021-09-16 9:19 ` Jakub Jelinek
2021-09-16 14:49 ` Qing Zhao
2021-09-16 14:56 ` Jakub Jelinek
2021-09-16 15:39 ` Qing Zhao
2021-09-16 15:47 ` Jakub Jelinek
2021-09-16 17:11 ` Qing Zhao
2021-09-16 17:39 ` Iain Sandoe
2021-09-16 18:55 ` Qing Zhao
2021-09-06 10:16 ` [patch][version 8]add -ftrivial-auto-var-init and variable attribute "uninitialized" to gcc Richard Biener
2021-09-07 16:57 ` Qing Zhao
2021-09-07 18:33 ` Qing Zhao
2021-09-09 22:49 ` [COMMITTED][patch][version 9]add " Qing Zhao
2021-09-09 23:10 ` Kees Cook
2021-09-10 7:23 ` Richard Biener
2021-09-10 13:46 ` Jose E. Marchesi
2021-09-10 14:36 ` Qing Zhao
2021-09-13 9:32 ` Richard Biener
2021-09-13 14:38 ` Jose E. Marchesi [this message]
2021-09-10 8:47 ` Christophe LYON
2021-09-10 9:08 ` Martin Liška
2021-09-10 14:01 ` Jeff Law
2021-09-10 9:40 ` Thomas Schwinge
2021-09-10 14:30 ` Qing Zhao
2021-09-10 14:26 ` Qing Zhao
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=87ee9sa6cf.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=keescook@chromium.org \
--cc=rguenther@suse.de \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
/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).