public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Keith.S.Thompson at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/61502] == comparison on "one-past" pointer gives wrong result Date: Tue, 21 Oct 2014 23:55:00 -0000 [thread overview] Message-ID: <bug-61502-4-DhTfespJPS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61502-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61502 --- Comment #8 from Keith Thompson <Keith.S.Thompson at gmail dot com> --- I'm not (deliberately) considering anything other than the requirements of the C standard. The standard talks about an array object immediately following another array object in the address space. Since that phrase is used in normative wording in the standard, I presume it's meaningful. Since the term is not otherwise defined, I presume that the intended meaning is one that follows reasonably clearly from the wording. The test program for Bug 63611, when I execute it, prints the string "y immediately follows x", followed by the string "inconsistent behavior:". Are you saying it's possible that y immediately follows x in the address space when that line of output is printed, and that y *doesn't* immediately follow x in the address space when "inconsistent behavior:" is printed? If so, can you describe what the word "follows" means in this context? If it has a meaning that permits such behavior, can you cite a source that indicates that that's how the authors of the standard meant it?
next prev parent reply other threads:[~2014-10-21 23:37 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-13 15:59 [Bug c/61502] New: " Peter.Sewell at cl dot cam.ac.uk 2014-06-13 19:29 ` [Bug c/61502] " joseph at codesourcery dot com 2014-06-13 22:59 ` joseph at codesourcery dot com 2014-06-14 8:00 ` harald at gigawatt dot nl 2014-10-21 21:44 ` [Bug tree-optimization/61502] " jsm28 at gcc dot gnu.org 2014-10-21 22:32 ` Keith.S.Thompson at gmail dot com 2014-10-21 23:17 ` joseph at codesourcery dot com 2014-10-21 23:55 ` Keith.S.Thompson at gmail dot com [this message] 2014-10-22 1:48 ` joseph at codesourcery dot com 2014-10-22 2:48 ` Keith.S.Thompson at gmail dot com 2014-10-22 8:40 ` rguenth at gcc dot gnu.org 2014-10-22 16:55 ` harald at gigawatt dot nl 2014-10-22 17:25 ` joseph at codesourcery dot com 2014-10-26 18:30 ` Keith.S.Thompson at gmail dot com 2014-10-27 18:28 ` joseph at codesourcery dot com 2015-04-07 8:45 ` rguenth at gcc dot gnu.org 2021-11-21 4:46 ` pinskia at gcc dot gnu.org 2021-11-21 4:49 ` pinskia at gcc dot gnu.org 2023-07-01 16:26 ` egallager at gcc dot gnu.org 2024-01-26 13:17 ` vincent-gcc at vinc17 dot net
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-61502-4-DhTfespJPS@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: linkBe 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).