public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "s__nakayama at infoseek dot jp" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/26534] New: bitfield wrong optimize Date: Thu, 02 Mar 2006 21:23:00 -0000 [thread overview] Message-ID: <bug-26534-10812@http.gcc.gnu.org/bugzilla/> (raw) #include <stdio.h> struct X { unsigned a:4; }; int main() { struct X x = { 63u }; printf("%u\n", x.a); return 0; } // end. result: g++ bug.cpp; ./a 15 g++ -O bug.cpp; ./a 63 wrong result!! -- Summary: bitfield wrong optimize Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: s__nakayama at infoseek dot jp http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26534
next reply other threads:[~2006-03-02 21:23 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-02 21:23 s__nakayama at infoseek dot jp [this message] 2006-03-02 21:35 ` [Bug tree-optimization/26534] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-03-03 12:07 ` [Bug c++/26534] " rguenth at gcc dot gnu dot org 2006-04-08 18:56 ` pinskia at gcc dot gnu dot org 2006-04-16 18:41 ` mmitchel at gcc dot gnu dot org 2006-04-18 15:27 ` bonzini at gnu dot org 2006-04-19 17:12 ` mmitchel at gcc dot gnu dot org 2006-04-22 22:14 ` mmitchel at gcc dot gnu dot org 2006-04-23 3:16 ` mmitchel at gcc dot gnu dot org 2006-04-23 18:04 ` mmitchel at gcc dot gnu dot org 2006-04-23 18:05 ` [Bug c++/26534] [4.1] " mmitchel at gcc dot gnu dot org 2006-05-01 2:18 ` mmitchel at gcc dot gnu dot org 2006-05-01 2:18 ` mmitchel 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=bug-26534-10812@http.gcc.gnu.org/bugzilla/ \ --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).