[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae25b7b1efcfe4eda9465c4fb4712ede928a33c4.camel@perches.com>
Date: Tue, 31 Mar 2020 12:00:25 -0700
From: Joe Perches <joe@...ches.com>
To: Rasmus Villemoes <rasmus.villemoes@...vas.dk>,
Vegard Nossum <vegard.nossum@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org,
Daniel Santos <daniel.santos@...ox.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Ian Abbott <abbotti@....co.uk>
Subject: Re: [PATCH] compiler.h: fix error in BUILD_BUG_ON() reporting
On Tue, 2020-03-31 at 20:56 +0200, Rasmus Villemoes wrote:
> On 31/03/2020 20.20, Joe Perches wrote:
> > On Tue, 2020-03-31 at 13:26 +0200, Vegard Nossum wrote:
> > > #define compiletime_assert(condition, msg) \
> > > - _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
> > > + _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> >
> > This might be better using something like __LINE__ ## _ ## __COUNTER__
> >
> > as line # is somewhat useful to identify the specific assert in a file.
> >
>
> Eh, if the assert fires, doesn't the compiler's diagnostics already
> contain all kinds of location information?
I presume if that were enough,
neither __LINE__ nor __COUNTER__
would be useful.
Powered by blists - more mailing lists