On Sun, 20 Oct 2013, matthew green wrote:
as part of the GCC 4.8 preparation work, we're seeing many new
warnings where variables are only used inside KASSERT(), but the
non-diag kernel builds trigger errors.
my solution, rather than marking these variables with __USE(),
is to change KASSERT(
hi folks.
as part of the GCC 4.8 preparation work, we're seeing many new
warnings where variables are only used inside KASSERT(), but
the non-diag kernel builds trigger errors.
my solution, rather than marking these variables with __USE(),
is to change KASSERT() into a real function that consum
