From: "Laszlo Ersek" <lersek@redhat.com>
To: "vit9696@protonmail.com" <vit9696@protonmail.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH] MdePkg: Add STATIC_ASSERT macro
Date: Wed, 14 Aug 2019 17:30:22 +0200 [thread overview]
Message-ID: <092e84c1-b966-7fa3-f202-fb813172e840@redhat.com> (raw)
In-Reply-To: <45B1F80A-14DF-4300-BE67-FE408398DDEE@protonmail.com>
(adding back the list)
On 08/13/19 16:30, vit9696@protonmail.com wrote:
> Laszlo,
>
> GCC implemented _Static_assert in 4.6. See its official wiki for C11 compatibility documentation:
>
> https://gcc.gnu.org/wiki/C11Status
Awesome news!
Once this is upstreamed, we should go through all the ASSERT()s in the
code, and replace those that are compile-time checkable with
STATIC_ASSERT(). I know that I've added quite a few ASSERT()s that I
wished would be checked at build time.
Of course, I'll probably never have time for that. :/
Thanks
Laszlo
prev parent reply other threads:[~2019-08-14 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 10:05 [PATCH] MdePkg: Add STATIC_ASSERT macro vit9696
2019-08-12 21:12 ` [edk2-devel] " Michael D Kinney
2019-08-13 12:28 ` Laszlo Ersek
[not found] ` <45B1F80A-14DF-4300-BE67-FE408398DDEE@protonmail.com>
2019-08-14 15:30 ` Laszlo Ersek [this message]
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-list 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=092e84c1-b966-7fa3-f202-fb813172e840@redhat.com \
--to=devel@edk2.groups.io \
/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