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 lto/112716] LTO optimization with struct with variable size Date: Mon, 27 Nov 2023 08:13:17 +0000 [thread overview] Message-ID: <bug-112716-4-HQ4fI5fcri@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112716-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112716 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Not that local types are never "merged" for cross-TU aliasing, they keep being distinct types. In particular this applies to VLA types since the reference to function-local vars ties them to the function IL sections and thus they do not become subject to global var/type unification. If it's undefined in C then the behavior is OK and expected. I don't think the C standard requirement can extend to VLA types this way.
next prev parent reply other threads:[~2023-11-27 8:13 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-26 17:46 [Bug lto/112716] New: LTO optimization with struct of variable ssize muecker at gwdg dot de 2023-11-26 17:54 ` [Bug lto/112716] " pinskia at gcc dot gnu.org 2023-11-26 18:17 ` uecker at gcc dot gnu.org 2023-11-26 18:26 ` sjames at gcc dot gnu.org 2023-11-27 8:13 ` rguenth at gcc dot gnu.org [this message] 2023-11-27 14:00 ` [Bug lto/112716] LTO optimization with struct with variable size muecker at gwdg dot de 2023-11-27 14:26 ` rguenther at suse dot de 2023-11-27 15:47 ` uecker at gcc dot gnu.org 2023-11-28 8:02 ` rguenth at gcc dot gnu.org 2023-11-28 15:19 ` muecker at gwdg dot de
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-112716-4-HQ4fI5fcri@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).