Re: "eliminate warn_on_slowpath()" change causes many gcc-3.2.3warnings

[Linus Torvalds]

On Sat, 17 Jan 2009, Kyle McMartin wrote:
> 
> How about something utterly evil? (Since you can't pass a zero-length
> string to a printf attributed function either...)

Don't do this. That just forces a load off a complex pointer instead, with 
no upsides. At least if it was

	extern const char warn_slowpath_nofmt[];

it would only load the pointer itself, which is still a fairly  expensive 
op, but at least doesn't require the extra memory load.

But you'd be better off jusst making it something like

	#define NO_FMT ((const char *)(-1))

instead, which is really much more obvious, and doesn't need any of that 
"get a pointer" overhead.

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/