linux-kernel - Re: [PATCH] static_assert: move before people start using it

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0c040ccc-e32d-253f-f764-766e5cec063f@rasmusvillemoes.dk>
Date:   Sun, 10 Mar 2019 23:09:13 +0100
From:   Rasmus Villemoes <linux@...musvillemoes.dk>
To:     Alexey Dobriyan <adobriyan@...il.com>
Cc:     akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] static_assert: move before people start using it

On 10/03/2019 22.30, Alexey Dobriyan wrote:
> and BUILD_BUG is bad). Once everything is converted to static_assert(),

That will never happen, because the two are not interchangeable
[ignoring the churn it would involve]. BUILD_BUG_ON can eat expressions
which static_assert won't (e.g. BUILD_BUG_ON(cnt - label1 != OFFSET1);,
where cnt and label1 are definitely not ICEs). Which is one of the
reasons the kernel cannot be built without optimizations.