public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neoxic at icloud dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106939] Linker-defined symbols are stained due to 'array subscript is partly outside array bounds' warning
Date: Sat, 24 Sep 2022 01:21:32 +0000	[thread overview]
Message-ID: <bug-106939-4-soZuBsRxRr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106939-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Arseny Vakhrushev <neoxic at icloud dot com> ---
Thank you, Jakub! I have read that section and can see that the Standard is
just very cautious about the cases it doesn't cover labeling them as "undefined
behaviour". The most likely reason is memory segmentation. Comparing two
pointers that point to different objects located in different memory segments
make no sense. But taking into account that the times of segmented memory are
long gone for the average C programmer, it is save to assume that no additional
action is needed to fool the compiler.

      parent reply	other threads:[~2022-09-24  1:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  5:12 [Bug c/106939] New: " neoxic at icloud dot com
2022-09-14  5:18 ` [Bug c/106939] " pinskia at gcc dot gnu.org
2022-09-14  5:22 ` neoxic at icloud dot com
2022-09-14  5:38 ` pinskia at gcc dot gnu.org
2022-09-14  5:50 ` neoxic at icloud dot com
2022-09-14 16:09 ` pinskia at gcc dot gnu.org
2022-09-14 18:41 ` neoxic at icloud dot com
2022-09-22 19:26 ` jakub at gcc dot gnu.org
2022-09-24  1:21 ` neoxic at icloud dot com [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-106939-4-soZuBsRxRr@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).