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 tree-optimization/111750] Spurious -Warray-bounds warning when using member function pointers
Date: Tue, 10 Oct 2023 01:35:29 +0000	[thread overview]
Message-ID: <bug-111750-4-TpeM6bJU9A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111750-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> That this source produces a -Warray-bounds warning is somewhat surprising since it contains no arrays, no array indexing, and no pointer arithmetic

Well techincally there is pointer arithmetic because the pointer to member
function could have a delta for the function call at `(c.*func)();`
Also there is an "array" because all variables/decls are arrays in C++ with a
size of 1 (that allows you do pass &a + 1 as the end for iterators).

Anyways the problem here is the optimizer optimized &g into `(c.*func)();` but
had not optimized the  &MyClass::my_method part yet when the warning happened.

      reply	other threads:[~2023-10-10  1:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 23:53 [Bug tree-optimization/111750] New: " abbeyj+gcc at gmail dot com
2023-10-10  1:35 ` pinskia at gcc dot gnu.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-111750-4-TpeM6bJU9A@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).