public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tangyixuan at mail dot dlut.edu.cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115582] [15 regression] wrong code when accessing members of incompatible type structure Date: Fri, 21 Jun 2024 15:39:23 +0000 [thread overview] Message-ID: <bug-115582-4-BNYU9CABRn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115582-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115582 --- Comment #4 from tangyixuan <tangyixuan at mail dot dlut.edu.cn> --- Thanks for your concerns. The type of "a.x" is converted to char in "(char *)a + 1", and it may be confused in clang under -O0 vs -O{2,3}. gcc-15 outputs the "int" value, but the previous versions like gcc-5.3 produce the "char" value I guess.
next prev parent reply other threads:[~2024-06-21 15:39 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-21 13:48 [Bug tree-optimization/115582] New: [regression 15] " tangyixuan at mail dot dlut.edu.cn 2024-06-21 14:05 ` [Bug tree-optimization/115582] [15 regression] " sjames at gcc dot gnu.org 2024-06-21 14:11 ` pinskia at gcc dot gnu.org 2024-06-21 14:13 ` sjames at gcc dot gnu.org 2024-06-21 15:39 ` tangyixuan at mail dot dlut.edu.cn [this message] 2024-06-21 15:56 ` pinskia at gcc dot gnu.org 2024-06-27 1:37 ` xry111 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-115582-4-BNYU9CABRn@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).