From: Aaron Conole <aconole@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jason Baron <jbaron@akamai.com>,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH v2] printk: help pr_debug and pr_devel to optimize out arguments
Date: Wed, 09 Dec 2015 10:13:26 -0500 [thread overview]
Message-ID: <f7tbn9zhcyx.fsf@aconole.bos.csb> (raw)
In-Reply-To: <1652262.soph10NRXK@wuerfel> (Arnd Bergmann's message of "Wed, 09 Dec 2015 12:52:38 +0100")
Arnd Bergmann <arnd@arndb.de> writes:
> On Friday 04 December 2015 16:51:42 Aaron Conole wrote:
>> --- a/include/linux/printk.h
>> +++ b/include/linux/printk.h
>> @@ -106,13 +106,14 @@ struct va_format {
>>
>> /*
>> * Dummy printk for disabled debugging statements to use whilst maintaining
>> - * gcc's format and side-effect checking.
>> + * gcc's format checking.
>> */
>> -static inline __printf(1, 2)
>> -int no_printk(const char *fmt, ...)
>> -{
>> - return 0;
>> -}
>> +#define no_printk(fmt, ...) \
>> +do { \
>> + if (0) { \
>> + printk(fmt, ##__VA_ARGS__); \
>> + } \
>> +} while (0)
>>
>
> This change breaks compiling lib/842/, at least in some configurations:
>
> lib/842/842_decompress.c: In function '__do_index':
> lib/842/842_decompress.c:205:12422: error: implicit declaration of function 'no_printk'
>
> Using a gcc style vararg macro instead of the C99 style makes it work, but
> I don't know why the original version didn't work.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> diff --git a/include/linux/printk.h b/include/linux/printk.h
> index cc3803a8f73e..4d1851a82254 100644
> --- a/include/linux/printk.h
> +++ b/include/linux/printk.h
> @@ -108,10 +108,10 @@ struct va_format {
> * Dummy printk for disabled debugging statements to use whilst maintaining
> * gcc's format checking.
> */
> -#define no_printk(fmt, ...) \
> +#define no_printk(arg ...) \
> do { \
> if (0) { \
> - printk(fmt, ##__VA_ARGS__); \
> + printk(arg); \
> } \
> } while (0)
>
Ugh. Sorry about this; I thought I had compiled everywhere but I guess not.
next prev parent reply other threads:[~2015-12-09 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 22:45 [PATCH] printk: fix pr_debug and pr_devel to elide function calls Aaron Conole
2015-12-03 23:13 ` Joe Perches
2015-12-04 16:31 ` Jason Baron
2015-12-04 16:38 ` Aaron Conole
2015-12-04 16:46 ` Joe Perches
2015-12-04 21:51 ` [PATCH v2] printk: help pr_debug and pr_devel to optimize out arguments Aaron Conole
2015-12-09 11:52 ` Arnd Bergmann
2015-12-09 15:13 ` Aaron Conole [this message]
2015-12-09 15:47 ` Joe Perches
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=f7tbn9zhcyx.fsf@aconole.bos.csb \
--to=aconole@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jbaron@akamai.com \
--cc=joe@perches.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®