public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gniibe at fsij dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102151] Spurious warning by -Warray-bounds when allocating with flexible array member
Date: Thu, 02 Sep 2021 02:34:38 +0000	[thread overview]
Message-ID: <bug-102151-4-L6XrE9hGIN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102151-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102151

--- Comment #4 from Niibe Yutaka <gniibe at fsij dot org> ---
Thank you for the explanation.  I understand how (current version of) GCC
warns.

>From the viewpoint of use of structure with flexible array member, still, this
could be considered as a bug of GCC, because the warning itself is irrelevant.

My point is that:

(1) In the test case, use of offsetof(struct arg_and_data_s, arg) is valid (I
mean, no violation of language/feature).  In other words,

(2) Allocated space for an object of the structure may be smaller than
sizeof().  There are such cases, for structure with flexible array member,
because of structure alignment.

(3) It seems for me that by (current version of) GCC, the fact (2) is ignored.

      parent reply	other threads:[~2021-09-02  2:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  1:42 [Bug c/102151] New: " gniibe at fsij dot org
2021-09-01  1:58 ` [Bug c/102151] " gniibe at fsij dot org
2021-09-01  2:48 ` [Bug tree-optimization/102151] " pinskia at gcc dot gnu.org
2021-09-01 15:02 ` msebor at gcc dot gnu.org
2021-09-02  2:34 ` gniibe at fsij dot org [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=bug-102151-4-L6XrE9hGIN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).