public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc bug
Date: Fri, 26 Jan 2001 09:40:22 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005106@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005105@msgid-missing>

On Fri, 26 Jan 2001 00:09:55 -0800, 
David Mosberger <davidm@hpl.hp.com> wrote:
>The attached program demonstrates a gcc code generation bug.
>
>struct f {
>  unsigned long lo : 32;
>  unsigned long hi : 32;
>};

K&R says "Fields may be declared only as ints".  The C99 rational says
"Three types of bit fields are now defined: plain int calls for
implementation-defined signedness (as in K&R), signed int calls for
assuredly signed fields, and unsigned int calls for unsigned fields".
I am surprised that the compiler accepted unsigned long, it is not
listed as a gcc extension.  Do you get the same error when those fields
are changed to unsigned int?



  reply	other threads:[~2001-01-26  9:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26  8:09 [Linux-ia64] gcc bug David Mosberger
2001-01-26  9:40 ` Keith Owens [this message]
2001-01-27  4:20 ` Jim Wilson
2001-01-27  5:21 ` David Mosberger

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=marc-linux-ia64-105590693005106@msgid-missing \
    --to=kaos@ocs.com.au \
    --cc=linux-ia64@vger.kernel.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: link
Be 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