public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Charlie Skilbeck" <charlie@skilbeck.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6874: deriving from zero-sized objects causes extraneous padding Date: Fri, 07 Jun 2002 19:06:00 -0000 [thread overview] Message-ID: <20020608020602.24177.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6874; it has been noted by GNATS. From: "Charlie Skilbeck" <charlie@skilbeck.com> To: <lerdsuwa@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <gnubug@skilbeck.com>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/6874: deriving from zero-sized objects causes extraneous padding Date: Fri, 7 Jun 2002 19:04:10 -0700 Sadly, upgrading to the the beta 3.0 compiler is not an option at this stage of our project (the mips version is unstable) - can someone point me at the relevant source file, and I'll fix it myself... Cheers, Charlie. ----- Original Message ----- From: <lerdsuwa@gcc.gnu.org> To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <gnubug@skilbeck.com>; <nobody@gcc.gnu.org> Sent: Fri, Jun 07, 2002 7:25 AM Subject: Re: c++/6874: deriving from zero-sized objects causes extraneous padding > Synopsis: deriving from zero-sized objects causes extraneous padding > > State-Changed-From-To: open->closed > State-Changed-By: lerdsuwa > State-Changed-When: Fri Jun 7 07:25:37 2002 > State-Changed-Why: > GCC 3.0 and later (with the new V3 ABI) behave like > the suggested idea. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p r=6874 > >
next reply other threads:[~2002-06-08 2:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-07 19:06 Charlie Skilbeck [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-07 7:25 lerdsuwa 2002-05-30 16:06 gnubug
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=20020608020602.24177.qmail@sources.redhat.com \ --to=charlie@skilbeck.com \ --cc=gcc-prs@gcc.gnu.org \ --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).