From: James E Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: curious compiler-warning
Date: Tue, 12 Jul 2005 01:55:22 +0000 [thread overview]
Message-ID: <1121133322.9211.75.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <ed5aea430507111600684085cc@mail.gmail.com>
On Mon, 2005-07-11 at 16:00, david mosberger wrote:
> arch/ia64/kernel/time.c:198: warning: format '%u' expects type
> 'unsigned int', but argument 5 has type 'unsigned int'
> Argument 5 here is a bit field declared as:
> unsigned long field : 32;
This looks like a bug to me. There have been some significant changes
to the bit-field support over the last few years. There were some cases
where we were non-conforming with respect to C89: getting sign/zero
extension wrong, performing operations with the wrong precision. Plus
some changes were needed for C99 support. It looks like these changes
have accidentally broken the -Wformat support.
Just taking a quick look, I don't see any existing bug report for this,
so I created a new one. This is now FSF gcc bug 22421.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id"421
next prev parent reply other threads:[~2005-07-12 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 23:00 curious compiler-warning david mosberger
2005-07-12 1:55 ` James E Wilson [this message]
2005-07-12 4:17 ` 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=1121133322.9211.75.camel@aretha.corp.specifix.com \
--to=wilson@tuliptree.org \
--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