public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: grigory@stl.sarov.ru To: gcc-gnats@gcc.gnu.org Subject: c++/7432: Changed bitfield allocation strategy in g++ 3.1.1 Date: Mon, 29 Jul 2002 05:26:00 -0000 [thread overview] Message-ID: <20020729122433.22622.qmail@sources.redhat.com> (raw) >Number: 7432 >Category: c++ >Synopsis: Changed bitfield allocation strategy in g++ 3.1.1 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jul 29 05:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Grigory Zagorodnev >Release: 3.1.1 >Organization: >Environment: host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ./configure --enable-threads >Description: Attached test case expecting the size of complete structure C to be 16 bytes. struct C { char c; int i : 67; char d; }; This is what been offered by GNU compiler for a long time. GCC 3.1.1 compiler gives another size of the structure (24 bytes). I do not see any reason to enlarge space taken by the structure C, moreover I do not see any ABI acknowledgment for this. So, the bitfield allocation strategy looks to be erroneously changed. >How-To-Repeat: $g++ foo.cpp $a.out Actuall results (output): sizeof(C) = 24 offsetof(C, d) = 17 Expected results (output): sizeof(C) = 16 offsetof(C, d) = 13 >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-07-29 12:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-29 5:26 grigory [this message] 2002-07-29 8:50 nathan 2002-07-29 10:52 nathan 2002-07-29 10:56 Nathan Sidwell
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=20020729122433.22622.qmail@sources.redhat.com \ --to=grigory@stl.sarov.ru \ --cc=gcc-gnats@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).