curious compiler-warning
Hi Jim,
I tried to make the ia64-specific files in the Linux kernel compile cleanly with gcc v4.0.1 and ended up with this curious warning message:
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;
and if I use a format of '%lu' (what we used so far), I also get a warning, which wasn't the case with pre-4.x compilers.
Do you know what's wrong here?
Thanks,
--david
Quoted 4 lines · david mosberger
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
Thanks for creating the bug-report the analysis --- interesting read!
--david
Quoted 20 lines · James E Wilson
Quoted 4 lines · david mosberger
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