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 c/107010] iterate section("mysection") struct mystruct fails if first node is const and compiling with O2 or greater Date: Thu, 22 Sep 2022 19:18:12 +0000 [thread overview] Message-ID: <bug-107010-4-lvKCSeHst3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107010-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107010 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=77964 Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- That is because GCC knows that first+1 does not point to a valid pointer really. You need to hide the assignment of iterator from GCC. This will fix the issue: const struct linkinfostruct *iterator = &first; asm("":"+r"(iterator)); while (iterator->name) { fprintf (stderr, "name=%s\n", iterator->name); iterator++; fprintf (stderr, " next iteration should be (iterator=%p, &iterator->name=%p name=%p \"%s\"\n", iterator, &iterator->name, iterator->name, iterator->name); } See PR 77964 and PR 106939 also.
next prev parent reply other threads:[~2022-09-22 19:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-22 19:12 [Bug c/107010] New: " stian.skjelstad at gmail dot com 2022-09-22 19:18 ` pinskia at gcc dot gnu.org [this message] 2022-09-22 19:42 ` [Bug c/107010] " stian.skjelstad at gmail dot com
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-107010-4-lvKCSeHst3@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).