public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/7018: bitfield of type long long treated as int in shift Date: Thu, 10 Apr 2003 14:16:00 -0000 [thread overview] Message-ID: <20030410141600.16087.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/7018; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: gcc-gnats@gcc.gnu.org, jbeulich@novell.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org Cc: Subject: Re: middle-end/7018: bitfield of type long long treated as int in shift Date: Thu, 10 Apr 2003 16:09:28 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7018 This PR is about this piece of code and it complains that the bitfield is promoted to int instead of unsigned long long in the return statement: struct s { unsigned long long uf:1; }; unsigned long long utest(const struct s*ps) { return ps->uf << 32; } IMHO this is behaviour is correct but the standard is somewhat vague wrt. bit-fields of other types than _Bool, char and int, so I need a language lawyer to make the final decision. The standard does state quite clearly that an unsigned int bitfield with a width less than that of int has to be promoted to int and not to unsigend int, i.e. there is no implicit conversion of the bitfield to its "container type". regards Christian -- THAT'S ALL FOLKS!
next reply other threads:[~2003-04-10 14:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-10 14:16 Christian Ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-10 14:46 Andreas Schwab 2003-03-15 3:24 bangerth
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=20030410141600.16087.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).