public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113164] [missed optimization] struct fields should not alias Date: Mon, 08 Jan 2024 14:16:15 +0000 [thread overview] Message-ID: <bug-113164-4-UgYgeXBw75@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113164-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113164 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-01-08 Ever confirmed|0 |1 CC| |hubicka at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Status|UNCONFIRMED |NEW --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- This would rely on TBAA btw, with -fno-strict-aliasing we allow *a and *b to overlap, aka a = &b->b; confirmed. I think we have all the bits in aliasing_component_refs_p and friends, it just would need to be factored/wired up for addresses.
next prev parent reply other threads:[~2024-01-08 14:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-28 14:55 [Bug middle-end/113164] New: " powerboat9.gamer at gmail dot com 2023-12-28 18:22 ` [Bug middle-end/113164] " pinskia at gcc dot gnu.org 2024-01-08 14:16 ` rguenth at gcc dot gnu.org [this message] 2024-05-16 12:47 ` rguenth 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-113164-4-UgYgeXBw75@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).