linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
	kvm-ppc@vger.kernel.org, linux-next@vger.kernel.org,
	Jan Beulich <JBeulich@novell.com>,
	akpm@linux-foundation.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] BUILD_BUG_ON: make it handle more cases
Date: Thu, 22 Oct 2009 14:04:37 -0700	[thread overview]
Message-ID: <1256245477.7495.30.camel@slab.austin.ibm.com> (raw)
In-Reply-To: <200910201415.34361.rusty@rustcorp.com.au>

On Tue, 2009-10-20 at 14:15 +1030, Rusty Russell wrote:
> BUILD_BUG_ON used to use the optimizer to do code elimination or fail
> at link time; it was changed to first the size of a negative array (a
> nicer compile time error), then (in
> 8c87df457cb58fe75b9b893007917cf8095660a0) to a bitfield.
> 
> bitfields: needs a literal constant at parse time, and can't be put under
> 	"if (__builtin_constant_p(x))" for example.
> negative array: can handle anything, but if the compiler can't tell it's
> 	a constant, silently has no effect.
> link time: breaks link if the compiler can't determine the value, but the
> 	linker output is not usually as informative as a compiler error.
> 
> If we use the negative-array-size method *and* the link time trick,
> we get the ability to use BUILD_BUG_ON() under __builtin_constant_p()
> branches, and maximal ability for the compiler to detect errors at
> build time.
> 
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

Thanks Rusty, this indeed fixes the problem.

Acked-by: Hollis Blanchard <hollisb@us.ibm.com>

-- 
Hollis Blanchard
IBM Linux Technology Center

  parent reply	other threads:[~2009-10-22 21:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29  9:28 linux-next: tree build failure Jan Beulich
2009-09-29  9:51 ` roel kluin
2009-09-30  6:29   ` Jan Beulich
2009-09-29 23:39 ` Hollis Blanchard
2009-09-30  6:35   ` Jan Beulich
2009-10-02 15:48     ` Hollis Blanchard
2009-10-05  6:58       ` Jan Beulich
2009-10-09 19:14         ` Hollis Blanchard
2009-10-14 22:57           ` Hollis Blanchard
2009-10-15  7:27             ` Jan Beulich
2009-10-19 18:19               ` Hollis Blanchard
2009-10-20  1:12                 ` Rusty Russell
2009-10-20  1:29                   ` Hollis Blanchard
2009-10-20  3:45                     ` [PATCH] BUILD_BUG_ON: make it handle more cases Rusty Russell
2009-10-20 13:58                       ` Américo Wang
2009-10-20 14:43                         ` Alan Jenkins
2009-10-23  1:50                           ` Américo Wang
2009-10-22 21:04                       ` Hollis Blanchard [this message]
2009-10-29 21:30                       ` Hollis Blanchard
2009-11-05  0:20                       ` Stephen Rothwell
2009-11-05  6:28                         ` Rusty Russell
2009-11-05  6:37                           ` Rusty Russell
2009-11-05  6:38                           ` Stephen Rothwell
2009-11-06  6:30                             ` Rusty Russell
2009-11-05  6:01                       ` Benjamin Herrenschmidt

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=1256245477.7495.30.camel@slab.austin.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=JBeulich@novell.com \
    --cc=akpm@linux-foundation.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).