public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at eyesopen dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/17112] Copying of packed bitfields is wrong Date: Thu, 23 Sep 2004 13:03:00 -0000 [thread overview] Message-ID: <20040923130340.13073.qmail@sourceware.org> (raw) In-Reply-To: <20040819232250.17112.gene@digilicious.com> ------- Additional Comments From roger at eyesopen dot com 2004-09-23 13:03 ------- As far as the RTL expansion is concerned the problem seems to be that we're wrapping a 32-bit component-ref around a 24-bit array-ref, such that bitsize in store_bit_field is 32. I've also confirmed that this behaviour is common to both the C and C++ front-ends. If the assignment is changed to y[1].int24 = x[1].int24 (in both C and C++) everything works as expected (though the generated code looks fairly hideous, but I know how to fix that :>). This is why the explicit assignment operator works in C++, it copies the field and not the structure. Now to work out where the component_ref with the incorrect tree type is coming from... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17112
next prev parent reply other threads:[~2004-09-23 13:03 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-19 23:22 [Bug c++/17112] New: default operator= for struct with packed bitfield " gene at digilicious dot com 2004-08-20 12:45 ` [Bug c++/17112] " bangerth at dealii dot org 2004-08-20 12:50 ` bangerth at dealii dot org 2004-08-20 20:23 ` gene at digilicious dot com 2004-09-23 2:48 ` [Bug middle-end/17112] Copying of packed bitfields " giovannibajo at libero dot it 2004-09-23 3:36 ` giovannibajo at libero dot it 2004-09-23 13:03 ` roger at eyesopen dot com [this message] 2004-09-23 13:16 ` giovannibajo at libero dot it 2004-09-23 13:29 ` roger at eyesopen dot com 2004-09-23 14:50 ` giovannibajo at libero dot it 2004-09-24 3:03 ` giovannibajo at libero dot it 2004-09-25 9:45 ` giovannibajo at libero dot it 2004-09-26 14:58 ` cvs-commit at gcc dot gnu dot org 2004-09-26 15:16 ` pinskia at gcc dot gnu dot org 2004-09-27 10:06 ` schwab at suse dot de 2004-09-27 10:09 ` schwab at suse dot de 2004-09-27 12:55 ` pinskia at gcc dot gnu dot org 2004-09-27 13:20 ` pinskia at gcc dot gnu dot org 2004-09-27 14:07 ` schwab at suse dot de
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=20040923130340.13073.qmail@sourceware.org \ --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).