public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d-ef at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102006] A false warning "Array subscript -N is outside array bounds warning"
Date: Mon, 23 Aug 2021 09:53:30 +0000	[thread overview]
Message-ID: <bug-102006-4-RBE20dGey4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102006-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Dmitriano <d-ef at yandex dot ru> ---
(In reply to Dmitriano from comment #7)
> (In reply to Richard Biener from comment #6)
> > It sounds like the usual upcasting of a link-only node which is strictly
> > non-conforming and can also result in TBAA issues but it's wide-spread. 
> > Note I didn't look into the source at all.
> 
> Yes it is a warning about upcasting, I cast a list node (or list link) of
> type Link to list element of type T. Theoretically Link should always be a
> subobject of T in my code.

Saying more exactly, Link should be a subobject of T when I cast it, but not
always.

  parent reply	other threads:[~2021-08-23  9:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-21 11:35 [Bug c++/102006] New: " d-ef at yandex dot ru
2021-08-21 12:46 ` [Bug c++/102006] " pinskia at gcc dot gnu.org
2021-08-21 13:19 ` d-ef at yandex dot ru
2021-08-21 13:20 ` d-ef at yandex dot ru
2021-08-21 13:23 ` d-ef at yandex dot ru
2021-08-21 18:21 ` [Bug tree-optimization/102006] " msebor at gcc dot gnu.org
2021-08-23  8:54 ` rguenth at gcc dot gnu.org
2021-08-23  9:50 ` d-ef at yandex dot ru
2021-08-23  9:53 ` d-ef at yandex dot ru [this message]
2021-08-27 16:59 ` msebor at gcc dot gnu.org
2021-08-27 17:00 ` msebor at gcc dot gnu.org
2022-02-16  1:33 ` d-ef at yandex dot ru
2022-02-16 17:25 ` 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-102006-4-RBE20dGey4@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).