public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "w at 1wt dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/98503] [11 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da
Date: Mon, 04 Jan 2021 16:17:13 +0000	[thread overview]
Message-ID: <bug-98503-4-oJ8B1mMCqT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98503-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Willy Tarreau <w at 1wt dot eu> ---
Hi Martin,

I'm sorry but I'm missing something, as this is how linked lists are
implemented everywhere nowadays. I'm not actually casting the pointer, it was
made for simplification. I'm only following the list elements which are linked
together from a list head accessed via a container_of.

The code does nothing but follow the list from the head (which is only a struct
list) and visiting all nodes in turn. There is absolutely zero dereference of a
list using a wrong pointer here.

  parent reply	other threads:[~2021-01-04 16:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03  7:53 [Bug c/98503] New: [11 regression] -Warray-bounds false positive with global variables at -O2 w at 1wt dot eu
2021-01-03  7:56 ` [Bug c/98503] " w at 1wt dot eu
2021-01-04 12:33 ` [Bug c/98503] [11 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da marxin at gcc dot gnu.org
2021-01-04 16:06 ` msebor at gcc dot gnu.org
2021-01-04 16:17 ` w at 1wt dot eu [this message]
2021-01-04 16:19 ` w at 1wt dot eu
2021-01-04 17:41 ` msebor at gcc dot gnu.org
2021-01-04 22:43 ` w at 1wt dot eu
2021-01-05 11:16 ` rguenth at gcc dot gnu.org
2021-01-05 11:34 ` w at 1wt dot eu
2021-01-05 17:31 ` msebor at gcc dot gnu.org
2021-01-28 23:06 ` [Bug middle-end/98503] " msebor at gcc dot gnu.org
2021-04-27 11:40 ` [Bug middle-end/98503] [11/12 " jakub at gcc dot gnu.org
2021-05-05 16:52 ` msebor at gcc dot gnu.org
2021-05-05 17:16 ` w at 1wt dot eu
2021-07-28  7:05 ` rguenth at gcc dot gnu.org
2021-11-17 22:34 ` msebor at gcc dot gnu.org
2022-03-08  0:03 ` msebor at gcc dot gnu.org
2022-03-23  8:31 ` rguenth at gcc dot gnu.org
2022-03-23  9:32 ` w at 1wt dot eu

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