public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis187 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/11885] [3.3 Regression] Problem with bitfields in packed structs Date: Tue, 12 Aug 2003 16:51:00 -0000 [thread overview] Message-ID: <20030812165127.20395.qmail@sources.redhat.com> (raw) In-Reply-To: <20030811210952.11885.stanrost@lcs.mit.edu> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11885 janis187 at us dot ibm dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at redhat dot com ------- Additional Comments From janis187 at us dot ibm dot com 2003-08-12 16:51 ------- The regression in PR 11885 was introduced or exposed on the 3.3 branch and mainline by this patch: --- gcc/gcc/ChangeLog --- 2003-03-31 Jason Merrill <jason@redhat.com> * stor-layout.c (update_alignment_for_field): Respect DECL_USER_ALIGN for zero-length bitfields, too. * c-decl.c (finish_struct): Don't set DECL_ALIGN for normal fields. --- gcc/gcc/cp/ChangeLog --- 2003-03-31 Jason Merrill <jason@redhat.com> * class.c (check_field_decl): Don't set DECL_ALIGN. The test case passes for mainline after this large patch: --- gcc/gcc/ChangeLog --- 2003-04-03 Jason Merrill <jason@redhat.com> * stor-layout.c (do_type_align): New fn, split out from... (layout_decl): ...here. Do all alignment calculations for FIELD_DECLs here. (update_alignment_for_field): Not here. (start_record_layout, debug_rli): Remove unpadded_align. * tree.h (struct record_layout_info_s): Remove unpadded_align. * c-decl.c (finish_enum): Don't set DECL_SIZE, DECL_ALIGN or DECL_MODE on the CONST_DECLs. (finish_struct): Don't mess with DECL_ALIGN. --- gcc/gcc/cp/ChangeLog --- 2003-04-03 Jason Merrill <jason@redhat.com> * class.c (build_vtable): Set DECL_ALIGN here. (get_vtable_decl): Not here. (layout_vtable_decl): Or here. (create_vtable_ptr): Or here. (layout_class_type): Or here. (check_bitfield_decl): Don't mess with field alignment. The hunts took place on i686-pc-linux-gnu using the submitter's test case.
next prev parent reply other threads:[~2003-08-12 16:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-11 21:09 [Bug c/11885] New: " stanrost at lcs dot mit dot edu 2003-08-11 21:14 ` [Bug c/11885] [3.3 Regression] " pinskia at gcc dot gnu dot org 2003-08-11 21:21 ` pinskia at gcc dot gnu dot org 2003-08-11 23:27 ` stanrost at lcs dot mit dot edu 2003-08-11 23:40 ` pinskia at gcc dot gnu dot org 2003-08-12 0:02 ` janis187 at us dot ibm dot com 2003-08-12 16:51 ` janis187 at us dot ibm dot com [this message] 2003-08-29 21:16 ` jason at gcc dot gnu dot org 2003-10-14 18:43 ` cvs-commit at gcc dot gnu dot org 2003-10-14 18:51 ` pinskia at gcc dot gnu dot org
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=20030812165127.20395.qmail@sources.redhat.com \ --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: 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).