public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/12625] bitfields which have sizes that are powers of 8 missed by -Wparentheses Date: Sun, 23 Apr 2006 20:05:00 -0000 [thread overview] Message-ID: <20060423200506.6999.qmail@sourceware.org> (raw) In-Reply-To: <bug-12625-4304@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from pinskia at gcc dot gnu dot org 2006-04-23 20:05 ------- Fixed by: 2006-04-23 Mark Mitchell <mark@codesourcery.com> PR c++/26534 * cp-tree.h (is_bitfield_expr_with_lowered_type): New function. * typeck.c (is_bitfield_expr_with_lowered_type): New function. (decay_conversion): Convert bitfield expressions to the correct type. (build_modify_expr): Remove spurious conversions. * class.c (layout_class_type): Modify the type of bitfields to indicate a limited range. * call.c (standard_conversion): Adjust the type of bitfield expressions used in an rvalue context. (build_conditional_expr): Likewise. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Target Milestone|--- |4.2.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12625
next parent reply other threads:[~2006-04-23 20:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-12625-4304@http.gcc.gnu.org/bugzilla/> 2006-04-23 20:05 ` pinskia at gcc dot gnu dot org [this message] 2003-10-15 18:07 [Bug c/12625] New: bitfields of size " nomura at netapp dot com 2004-07-20 15:15 ` [Bug c++/12625] bitfields which have sizes that are powers of " giovannibajo at libero dot it 2004-07-22 3:22 ` pinskia at gcc dot gnu dot org 2004-10-13 12:35 ` 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=20060423200506.6999.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).