public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100124] Why is "flexible array member '...' in an otherwise empty '...'" an issue?
Date: Tue, 20 Apr 2021 20:30:55 +0000	[thread overview]
Message-ID: <bug-100124-4-hWBAXPJSxZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100124-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Behdad Esfahbod from comment #6)
> > But I will note GCC treats (all) arrays at the end of a POD struct as a
> > flexible one so the question I have is more about the ubsan issue you are
> > running into, is that with GCC or with clang/LLVM?
> 
> The ubsan issue reported to us is with gcc:
> https://github.com/harfbuzz/harfbuzz/issues/2953#issuecomment-823460893

Can you report that as a bug as GCC's rule is treat all arrays that end a POD
as a flexiable array?  Please include the full preprocessed source that
produces the problem at runtime and the specific version of GCC that is used. 
This is a GCC bug in mind due to this unless there is another field missing
that is in the source that you are not showing.

  parent reply	other threads:[~2021-04-20 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 20:18 [Bug c/100124] New: " gcc at behdad dot org
2021-04-16 20:50 ` [Bug c++/100124] " pinskia at gcc dot gnu.org
2021-04-16 21:02 ` jakub at gcc dot gnu.org
2021-04-17  0:03 ` msebor at gcc dot gnu.org
2021-04-17  0:51 ` pinskia at gcc dot gnu.org
2021-04-17 21:13 ` msebor at gcc dot gnu.org
2021-04-20 19:32 ` gcc at behdad dot org
2021-04-20 20:30 ` pinskia at gcc dot gnu.org [this message]
2021-04-20 22:16 ` gcc at behdad dot org
2021-04-26 22:26 ` msebor 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-100124-4-hWBAXPJSxZ@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).