From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: "eliminate warn_on_slowpath()" change causes many gcc-3.2.3 warnings
Date: Sat, 17 Jan 2009 12:01:22 -0800 [thread overview]
Message-ID: <49723912.6020108@zytor.com> (raw)
In-Reply-To: <20090117161817.GA10825@elte.hu>
Ingo Molnar wrote:
>
> hm, that's unfortunate. GCC seems totally on crack for not accepting a
> NULL format string.
>
Why should it? I don't think a NULL pointer as the format to a
printf-style function is well defined.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-01-17 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 15:19 "eliminate warn_on_slowpath()" change causes many gcc-3.2.3 warnings Mikael Pettersson
2009-01-17 16:18 ` Ingo Molnar
2009-01-17 20:01 ` H. Peter Anvin [this message]
2009-01-17 20:44 ` Kyle McMartin
2009-01-17 20:57 ` Kyle McMartin
2009-01-17 21:07 ` H. Peter Anvin
2009-01-17 21:38 ` Kyle McMartin
2009-01-17 23:37 ` Linus Torvalds
2009-01-17 23:40 ` H. Peter Anvin
2009-01-18 0:01 ` Linus Torvalds
2009-01-18 0:10 ` H. Peter Anvin
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=49723912.6020108@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@elte.hu \
/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