public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Explorer09 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/115437] Wrong optimized code - GCC didn't detect a variable is modified Date: Tue, 11 Jun 2024 19:04:28 +0000 [thread overview] Message-ID: <bug-115437-4-fEG7wNYOgY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115437-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115437 --- Comment #3 from Kang-Che Sung <Explorer09 at gmail dot com> --- Now I come to realize that the C standard doesn't say that a pointer type is "compatible" with any other pointer type. So that "Foo **" type and "Bar **" type are assumed to never alias. This is troubling because I saw many APIs that would take a "pointer to pointer" argument in order to output address to a particular object (for example, asprintf()), and it would be difficult to write concise code while strictly conforming to the so-called strict aliasing rule.
prev parent reply other threads:[~2024-06-11 19:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-11 15:19 [Bug other/115437] New: " Explorer09 at gmail dot com 2024-06-11 15:25 ` [Bug other/115437] " pinskia at gcc dot gnu.org 2024-06-11 15:29 ` pinskia at gcc dot gnu.org 2024-06-11 19:04 ` Explorer09 at gmail 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-115437-4-fEG7wNYOgY@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).