public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uecker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/112716] LTO optimization with struct of variable ssize
Date: Sun, 26 Nov 2023 18:17:33 +0000	[thread overview]
Message-ID: <bug-112716-4-aWtDnbNN5E@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

uecker at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |uecker at gcc dot gnu.org

--- Comment #2 from uecker at gcc dot gnu.org ---
.
Inside the same TU there are different types.  But note that this is across TUs
where the structs with same tag and and compatible members are supposed to be
compatible (they could come from a shared header).  I would assume these rules
hold also for the GNU extension.  In C23 the structs will be compatible also
inside a TU (without GNU extensions, but I I think the same rules should then
also apply to structs with the GNU extension).

  parent reply	other threads:[~2023-11-26 18:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 17:46 [Bug lto/112716] New: " 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 [this message]
2023-11-26 18:26 ` sjames at gcc dot gnu.org
2023-11-27  8:13 ` [Bug lto/112716] LTO optimization with struct with variable size rguenth at gcc dot gnu.org
2023-11-27 14:00 ` 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-aWtDnbNN5E@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: link
Be 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).