From: "Wang, Cloud" <Cloud.Wang@amd.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] Do latest edk2 build tool support C99 standard
Date: Thu, 19 Sep 2019 22:52:56 +0000 [thread overview]
Message-ID: <MN2PR12MB3533D8D5B1EE9D9B3FFAE1A49D890@MN2PR12MB3533.namprd12.prod.outlook.com> (raw)
In-Reply-To: <b7a61c03-0ca4-3e2a-0fcd-eb7220fd1afc@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Ersek,
thanks for your information
获取 Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Laszlo Ersek <lersek@redhat.com>
Sent: Friday, September 20, 2019 4:32:20 AM
To: Wang, Cloud <Cloud.Wang@amd.com>
Cc: devel@edk2.groups.io <devel@edk2.groups.io>
Subject: Re: [edk2-devel] Do latest edk2 build tool support C99 standard
[CAUTION: External Email]
On 09/19/19 04:40, Wang, Cloud wrote:
> Dear Edk2 Base tool owner,
> Do latest edk2 build tool support C99 standard?
C source code in edk2 targets C95 in general. There are a few extensions
that are allowed (such as the __FUNCTION__ macro, "//"-style comments,
...), and there are some surprising restrictions too (no structure
assignment, no division / multiplication / bit-shifting for 64-bit
integers, no initialization except for static storage duration objects,
functions taking variable arguments must be EFIAPI, ...)
There is a coding style spec at
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Specifications#c-coding-standards
Thanks
Laszlo
[-- Attachment #2: Type: text/html, Size: 2543 bytes --]
prev parent reply other threads:[~2019-09-19 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 2:40 Do latest edk2 build tool support C99 standard Wang, Cloud
2019-09-19 20:32 ` [edk2-devel] " Laszlo Ersek
2019-09-19 22:52 ` Wang, Cloud [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=MN2PR12MB3533D8D5B1EE9D9B3FFAE1A49D890@MN2PR12MB3533.namprd12.prod.outlook.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