From: Rusty Russell <rusty@rustcorp.com.au>
To: Jan Beulich <JBeulich@suse.com>, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] utilize _Static_assert() for BUILD_BUG_ON() when the compiler supports it
Date: Mon, 05 Nov 2012 12:49:11 +1030 [thread overview]
Message-ID: <87pq3syeow.fsf@rustcorp.com.au> (raw)
In-Reply-To: <5093EB1C02000078000A61D7@nat28.tlf.novell.com>
Jan Beulich <JBeulich@suse.com> writes:
> This makes the resulting diagnostics quite a bit more useful.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Nice. I'm a bit disappointed we can't just treat _Static_assert() as
void, like:
#define BUILD_BUG_ON_ZERO(e) (_Static_assert(!(e), "!(" #e ")"), 0)
> @@ -54,6 +61,15 @@ struct pt_regs;
> */
> #ifndef __OPTIMIZE__
> #define BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
> +#elif __GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 3)
> +#define __build_bug_on_failed(n) __build_bug_on_##n##_failed
> +#define _BUILD_BUG_ON(n, condition) \
> + do { \
> + extern void __compiletime_error(#condition) \
> + __build_bug_on_failed(n)(void); \
> + if (condition) __build_bug_on_failed(n)(); \
> + } while(0)
> +#define BUILD_BUG_ON(condition...) _BUILD_BUG_ON(__COUNTER__, ##condition)
> #else
> extern int __build_bug_on_failed;
> #define BUILD_BUG_ON(condition) \
Why does this depend on gcc version? Looks like residue from an attempt
to use _Static_assert here?
Thanks,
Rusty.
next prev parent reply other threads:[~2012-11-05 3:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 14:47 Jan Beulich
2012-11-05 2:19 ` Rusty Russell [this message]
2012-11-05 8:46 ` Jan Beulich
2012-11-05 22:29 ` Andrew Morton
2012-11-06 1:51 ` Rusty Russell
2012-11-06 9:23 ` Jan Beulich
2012-11-07 1:03 ` Rusty Russell
2012-11-07 8:05 ` Jan Beulich
2012-11-07 23:24 ` Rusty Russell
2012-12-13 0:29 ` Daniel Santos
2012-12-13 9:43 ` Jan Beulich
2012-12-13 21:20 ` Daniel Santos
2012-12-13 0:48 ` Daniel Santos
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=87pq3syeow.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--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
Powered by JetHome