From: Jakub Jelinek <jakub@redhat.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: David Rientjes <rientjes@google.com>,
Joe Perches <joe@perches.com>, Matthew Wilcox <matthew@wil.cx>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, gcc@gcc.gnu.org,
zadeck@naturalbridge.com
Subject: Re: [PATCH] linux/fs.h - Convert debug functions declared inline __attribute__((format (printf,x,y) to statement expression macros
Date: Thu, 28 Feb 2008 03:42:37 -0500 [thread overview]
Message-ID: <20080228084237.GU24887@devserv.devel.redhat.com> (raw)
In-Reply-To: <20080227235835.GA31048@atrey.karlin.mff.cuni.cz>
On Thu, Feb 28, 2008 at 12:58:35AM +0100, Jan Hubicka wrote:
> We probably also can simply allow inlining variadic functions not
> calling va_start. I must say that this option appeared to me but I was
> unable to think of any sane use case. This probably is one ;)
We already allow inlining variadic functions not calling va_start, already
3.2.x did that and so do all following gccs. In 4.3+
__builtin_va_arg_pack{,_len} support was added, so that you can even pass
the ... arguments to variable length functions, query their count etc.
Jakub
next prev parent reply other threads:[~2008-02-28 8:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 3:08 [PATCH] linux/kernel.h linux/device.h - Convert debug functions declared inline __attribute__((format (printf,x,y) to statement expression macros Joe Perches
2008-02-27 4:02 ` [PATCH] linux/fs.h " Joe Perches
2008-02-27 4:13 ` Matthew Wilcox
2008-02-27 4:55 ` Joe Perches
2008-02-27 5:44 ` David Rientjes
2008-02-27 5:44 ` David Rientjes
2008-02-27 6:54 ` Joe Perches
2008-02-27 7:38 ` David Rientjes
2008-02-27 7:38 ` David Rientjes
2008-02-27 22:58 ` David Rientjes
2008-02-27 22:58 ` David Rientjes
2008-02-27 23:58 ` Jan Hubicka
2008-02-28 8:28 ` David Rientjes
2008-02-28 8:28 ` David Rientjes
2008-02-28 8:42 ` Jakub Jelinek [this message]
2008-02-28 10:23 ` Jan Hubicka
2008-02-29 1:09 ` Joe Perches
2008-02-29 1:09 ` Joe Perches
2008-03-23 15:22 ` Denys Vlasenko
2008-03-24 19:52 ` Joe Perches
2008-03-24 19:52 ` 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=20080228084237.GU24887@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=zadeck@naturalbridge.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.