public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "foo at mailinator dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/40404] New: Comparison involving unsigned int:17 bitfield seems wrong Date: Wed, 10 Jun 2009 18:38:00 -0000 [thread overview] Message-ID: <bug-40404-17390@http.gcc.gnu.org/bugzilla/> (raw) #include <stdio.h> struct S { unsigned int ui17 : 17; } s; int main() { s.ui17 = 0x1ffff; printf("%x\n", (unsigned int)s.ui17); if (s.ui17 >= 0xfffffffeu) puts("FAIL"); return 0; } Maybe I don't understand GCC's rules for the promotion of bitfields, but it seems to me that s.ui17 should evaluate to ((unsigned int)0x1ffff), which is less than 0xfffffffeu, so "FAIL" should not be printed. But "FAIL" is printed. I can't explain why; it's almost as if GCC is truncating the rhs to 0x1fffe before doing the comparison! Changing s.ui17 from 17 bits to 15 bits makes the test pass (i.e., not print "FAIL"). I believe in that case GCC promotes s.ui17 to "unsigned short"... but that should undergo usual arithmetic conversion to "unsigned int" at which point we ought to see the same FAIL behavior happening. Reproduced with GCC 4.2.4 and 4.3.3. -- Summary: Comparison involving unsigned int:17 bitfield seems wrong Product: gcc Version: 4.3.3 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: foo at mailinator dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40404
next reply other threads:[~2009-06-10 18:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-10 18:38 foo at mailinator dot com [this message] 2009-06-10 18:41 ` [Bug c/40404] " pinskia at gcc dot gnu dot org 2009-06-10 20:15 ` rguenth at gcc dot gnu dot org 2009-06-10 20:26 ` rguenth at gcc dot gnu dot org 2009-06-12 20:41 ` mikpe at it dot uu dot se 2009-06-13 13:56 ` rguenth at gcc dot gnu dot org 2009-06-17 12:29 ` [Bug middle-end/40404] " rguenth at gcc dot gnu dot org 2009-06-17 12:31 ` rguenth at gcc dot gnu dot org 2009-06-17 13:06 ` rguenth at gcc dot gnu dot org 2009-06-17 13:07 ` rguenth 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-40404-17390@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).