public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, lex.augusteijn@philips.com, nobody@gcc.gnu.org Subject: Re: optimization/10208: [ABI] Empty structs have zero size in C, but not in C++ Date: Tue, 25 Mar 2003 16:26:00 -0000 [thread overview] Message-ID: <20030325161822.11735.qmail@sources.redhat.com> (raw) Old Synopsis: Empty structs removed by gcc but not by g++ New Synopsis: [ABI] Empty structs have zero size in C, but not in C++ State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Tue Mar 25 16:18:22 2003 State-Changed-Why: I can confirm this, for all versions since 2.95 up to present mainline (including -fabi-version=0). I don't know what is right, though. Someone with knowledge of the C and C++ ABIs should take a brief look at this. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10208
reply other threads:[~2003-03-25 16:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030325161822.11735.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=lex.augusteijn@philips.com \ --cc=nobody@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).