public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/101601] [12 Regression] -Warray-bounds triggers error: arrays of functions are not meaningful
Date: Fri, 23 Jul 2021 17:27:16 +0000 [thread overview]
Message-ID: <bug-101601-4-lJ8lw1DzYx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101601-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101601
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Status|NEW |ASSIGNED
Keywords| |diagnostic
Target Milestone|--- |12.0
Summary|[12 Regression] -Wall is |[12 Regression]
|reported as a build error |-Warray-bounds triggers
|(not warning): error: |error: arrays of functions
|arrays of functions are not |are not meaningful
|meaningful |
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
-Warray-bounds triggers the error while formatting the type of SSCall_fun. For
simplicity, it converts the type of each singleton object into a one-element
array of its type, but the code is wrong for function pointers.
next prev parent reply other threads:[~2021-07-23 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 15:01 [Bug c++/101601] New: [12 Regression] -Wall is reported as a build error (not warning): " slyfox at gcc dot gnu.org
2021-07-23 15:10 ` [Bug middle-end/101601] " mpolacek at gcc dot gnu.org
2021-07-23 15:55 ` slyfox at gcc dot gnu.org
2021-07-23 17:27 ` msebor at gcc dot gnu.org [this message]
2021-07-28 22:16 ` [Bug middle-end/101601] [12 Regression] -Warray-bounds triggers " cvs-commit at gcc dot gnu.org
2021-07-28 22:17 ` 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-101601-4-lJ8lw1DzYx@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).