public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107951] New: Invalid flexible array use not detected in nested structs by the C frontend
Date: Fri, 02 Dec 2022 13:28:15 +0000	[thread overview]
Message-ID: <bug-107951-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107951
           Summary: Invalid flexible array use not detected in nested
                    structs by the C frontend
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: siddhesh at gcc dot gnu.org
  Target Milestone: ---

The following program:

typedef struct {
  char pad;
  char data[];
} F2;

typedef struct {
  F2 flex;
  unsigned pad;
} S2;

#define NULL (void *) 0

__SIZE_TYPE__
nested_flexarray (__SIZE_TYPE__ n)
{
  S2 *p = __builtin_malloc (n);

  return __builtin_dynamic_object_size (p->flex.data, 1);
}

ends up treating data[] as a zero sized array in C instead of flagging an
error.  This is correctly handled in the C++ driver.

             reply	other threads:[~2022-12-02 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 13:28 siddhesh at gcc dot gnu.org [this message]
2022-12-02 14:44 ` [Bug c/107951] " rguenth at gcc dot gnu.org
2022-12-02 15:38 ` qinzhao at gcc dot gnu.org
2022-12-02 15:47 ` pinskia at gcc dot gnu.org
2022-12-02 15:50 ` pinskia at gcc dot gnu.org
2022-12-02 16:36 ` siddhesh at gcc dot gnu.org
2022-12-02 16:51 ` qinzhao at gcc dot gnu.org
2022-12-02 16:55 ` jakub at gcc dot gnu.org
2022-12-02 17:01 ` qinzhao at gcc dot gnu.org

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-107951-4@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).