public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drohr at jwdt dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102937] Miscompilation with -O3 and aliasing of char* and size_t Date: Mon, 25 Oct 2021 21:44:16 +0000 [thread overview] Message-ID: <bug-102937-4-fsvOu33dSP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102937-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102937 David Rohr <drohr at jwdt dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED CC| |drohr at jwdt dot org --- Comment #3 from David Rohr <drohr at jwdt dot org> --- thanks, makes me feel pretty stupid... I thought it is not a problem since char* may alias, but apparently size_t* may not alias char**... if I understood correctly...
next prev parent reply other threads:[~2021-10-25 21:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-25 21:02 [Bug c++/102937] New: " drohr at jwdt dot org 2021-10-25 21:17 ` [Bug c++/102937] " pinskia at gcc dot gnu.org 2021-10-25 21:19 ` pinskia at gcc dot gnu.org 2021-10-25 21:44 ` drohr at jwdt dot org [this message] 2021-10-25 21:52 ` pinskia 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-102937-4-fsvOu33dSP@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).