public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: degnbol@danbbs.dk, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, neil@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c/5929: gcc 2.95-3.04 miscompiles anonymous unions inside anonymous structs Date: Tue, 12 Mar 2002 15:36:00 -0000 [thread overview] Message-ID: <20020312233639.8140.qmail@sources.redhat.com> (raw) Synopsis: gcc 2.95-3.04 miscompiles anonymous unions inside anonymous structs Responsible-Changed-From-To: unassigned->neil Responsible-Changed-By: neil Responsible-Changed-When: Tue Mar 12 15:36:37 2002 Responsible-Changed-Why: Mine. State-Changed-From-To: open->closed State-Changed-By: neil State-Changed-When: Tue Mar 12 15:36:37 2002 State-Changed-Why: I fixed this for 3.1, which will give: neil@cat:/tmp$ ./a.out offset v1 = 0 offset v2 = 4 offset v3 = 8 offset u1 = 12 offset u2 = 12 neil@cat:/tmp$ http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5929
next reply other threads:[~2002-03-12 23:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-12 15:36 neil [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-12 15:06 degnbol
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=20020312233639.8140.qmail@sources.redhat.com \ --to=neil@gcc.gnu.org \ --cc=degnbol@danbbs.dk \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).