public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Qing Zhao <qing.zhao@oracle.com>
To: Kees Cook <keescook@chromium.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	jakub Jelinek <jakub@redhat.com>,
	richard Biener <rguenther@suse.de>,
	martin Sebor <msebor@gmail.com>,
	"joseph@codesourcery.com" <joseph@codesourcery.com>
Subject: Re: [GCC13][Patch][V2][2/2]Add a new option -fstrict-flex-array[=n] and attribute strict_flex_array(n) and use it in PR101836
Date: Tue, 2 Aug 2022 15:41:46 +0000	[thread overview]
Message-ID: <CDFC9A97-30F9-4075-88E8-46E1672903A2@oracle.com> (raw)
In-Reply-To: <202208020826.EFFB2E7410@keescook>

Thanks a lot for your testing on Linux Kernel.
Will work on the version 3 of this patch soon.

Qing

> On Aug 2, 2022, at 11:30 AM, Kees Cook <keescook@chromium.org> wrote:
> 
> On Tue, Jul 19, 2022 at 02:11:19PM +0000, Qing Zhao wrote:
>> From a09f39ded462611286a44d9e8273de8342673ba2 Mon Sep 17 00:00:00 2001
>> From: Qing Zhao <qing.zhao@oracle.com>
>> Date: Mon, 18 Jul 2022 18:12:26 +0000
>> Subject: [PATCH 2/2] Use new flag DECL_NOT_FLEXARRAY in __builtin_object_size
>> [PR101836]
>> 
>> Use new flag DECL_NOT_FLEXARRAY to determine whether the trailing array
>> of a structure is flexible array member in __builtin_object_size.
> 
> FWIW, with these patches I've done builds of the Linux kernel using
> the ...=3 level, and things are looking correct on our end. (There are,
> as expected, many places in Linux that need to be fixed, and that work
> is on-going, guided by this option's results.)
> 
> -Kees
> 
> -- 
> Kees Cook


      reply	other threads:[~2022-08-02 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 14:11 Qing Zhao
2022-07-28  7:28 ` Richard Biener
2022-07-29 14:23   ` Qing Zhao
2022-08-01  7:13     ` Richard Biener
2022-08-01 14:14       ` Qing Zhao
2022-08-02 15:30 ` Kees Cook
2022-08-02 15:41   ` Qing Zhao [this message]

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=CDFC9A97-30F9-4075-88E8-46E1672903A2@oracle.com \
    --to=qing.zhao@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=keescook@chromium.org \
    --cc=msebor@gmail.com \
    --cc=rguenther@suse.de \
    /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).