diff options
author | James Hogan <james.hogan@imgtec.com> | 2014-06-04 16:11:16 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-06-04 16:54:14 -0700 |
commit | 2c0d259e0e580dd95dd5d2d5aa4926169228d4a0 (patch) | |
tree | 485207a39d1ac910eb07567205bede64c28d8316 /virt/kvm/coalesced_mmio.h | |
parent | 00f01791e159ba7fb9d397c27d34377206157c6a (diff) | |
download | linux-2c0d259e0e580dd95dd5d2d5aa4926169228d4a0.tar.gz linux-2c0d259e0e580dd95dd5d2d5aa4926169228d4a0.tar.bz2 linux-2c0d259e0e580dd95dd5d2d5aa4926169228d4a0.zip |
compiler.h: avoid sparse errors in __compiletime_error_fallback()
Usually, BUG_ON and friends aren't even evaluated in sparse, but recently
compiletime_assert_atomic_type() was added, and that now results in a
sparse warning every time it is used.
The reason turns out to be the temporary variable, after it sparse no
longer considers the value to be a constant, and results in a warning and
an error. The error is the more annoying part of this as it suppresses
any further warnings in the same file, hiding other problems.
Unfortunately the condition cannot be simply expanded out to avoid the
temporary variable since it breaks compiletime_assert on old versions of
GCC such as GCC 4.2.4 which the latest metag compiler is based on.
Therefore #ifndef __CHECKER__ out the __compiletime_error_fallback which
uses the potentially negative size array to trigger a conditional compiler
error, so that sparse doesn't see it.
Signed-off-by: James Hogan <james.hogan@imgtec.com>
Cc: Johannes Berg <johannes.berg@intel.com>
Cc: Daniel Santos <daniel.santos@pobox.com>
Cc: Luciano Coelho <luciano.coelho@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'virt/kvm/coalesced_mmio.h')
0 files changed, 0 insertions, 0 deletions