[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080411152648.GK9785@ZenIV.linux.org.uk>
Date: Fri, 11 Apr 2008 16:26:48 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: Ingo Molnar <mingo@...e.hu>,
Stephen Rothwell <sfr@...b.auug.org.au>,
mingo <mingo@...hat.com>, tglx <tglx@...utronix.de>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for April 10 (arch/x86)
On Fri, Apr 11, 2008 at 08:19:01AM -0700, Randy Dunlap wrote:
> > It
> > is a totally uninteresting warning that we pass in a narrower type to
> > printk(). It cannot ever cause any bugs or problems. Why does gcc warn
> > about it?
>
> No idea about that part.
Er... That's kinda obvious - vararg function getting the wrong-sized
argument is *NOT* a harmless situation. And yes, it's certainly a bug -
gcc manages to recover by using the knowledge of printf() formats (i.e.
it guesses that we want a long long and does conversion), but try to
do
char *s = "%llx %c";
printf(s, 1, '.');
and watch the show...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists