public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "'Andrew Fish (afish@apple.com)'" <afish@apple.com>
Subject: Re: [edk2-devel] [Patch v2 10/11] EmulatorPkg: Enable CLANG9 tool chain
Date: Thu, 17 Oct 2019 05:21:14 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C325901@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E51D6F1@SHSMSX104.ccr.corp.intel.com>

> >
> >1. Why move the assignment to a later place? Can you explain a bit more?
> The hang issue here.
> 
> I investigate this issue more. The root cause is that GetProcessAffinityMask()
> API requires the 64bit pointer as the input for 64bit ARCH. So, the correct fix
> should declare ProcessAffinityMask and SystemAffinityMask as UINTN. I will
> update the patch.
> 
> (GetProcessAffinityMask (GetCurrentProcess (), &ProcessAffinityMask,
> &SystemAffinityMask))
> 

Thanks!

> >2. If CLANG9 is used in Linux, WinHost is still used. That seems not good.
> >
> Now, CLANG9 is for Windows Emulator only. The key problem is that there is
> no way to know which OS is used in DSC. So for now, I will add the limitation
> here. For long term, we need to think the way to support Emulator usage.
> 
It's nice to build correct OS-host module depending on compiler tool chain.
But if CLANG9 is a cross-host compiler tool chain, I don't think such need should
be met.
So I would prefer the patch doesn't assume CLANG9 is a hint to build Win host.
Which means when using CLANG9, developer needs to use another macro to
tell build tool which host to build.


> >
> >3. Why TftpDynamicCommand cannot be built with CLANG9?
> >
> CLANG9 supports RC section. I will update patch to remove this change.

Thanks.

  reply	other threads:[~2019-10-17  5:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15  0:26 [Patch v2 00/11] New Cross OS tool chain CLANG9 Liming Gao
2019-10-15  0:26 ` [Patch v2 01/11] BaseTools tools_def.template: Remove unnecessary $(DEST_DIR_DEBUG) path Liming Gao
2019-10-16  8:59   ` [edk2-devel] " Bob Feng
2019-10-15  0:26 ` [Patch v2 02/11] BaseTools tools_def: Add CLANG9 tool chain to directly generate PE image Liming Gao
2019-10-15  0:26 ` [Patch v2 03/11] BaseTools GenFw: Fix the issue to update the wrong size as SectionSize Liming Gao
2019-10-15  9:21   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-16  9:27   ` Bob Feng
2019-10-17  2:18     ` Liming Gao
2019-10-15  0:26 ` [Patch v2 04/11] MdePkg Base.h: Add definition for CLANG9 tool chain Liming Gao
2019-10-15  9:32   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-15  0:26 ` [Patch v2 05/11] MdePkg BaseIoLibIntrinsic: Remove __inline__ attribute for IO functions Liming Gao
2019-10-15  9:26   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-22  1:42   ` Michael D Kinney
2019-10-15  0:26 ` [Patch v2 06/11] MdeModulePkg LzmaCustomDecompressLib: Update macro to be same in CLANG tool Liming Gao
2019-10-16  2:05   ` [edk2-devel] " Wu, Hao A
2019-10-15  0:26 ` [Patch v2 07/11] MdeModulePkg RegularExpressionDxe: Disable warning for CLANG9 tool chain Liming Gao
2019-10-16  2:06   ` [edk2-devel] " Wu, Hao A
2019-10-15  0:26 ` [Patch v2 08/11] CryptoPkg: Append options to make CLANG9 tool chain pass build Liming Gao
2019-10-15  9:29   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-16  1:12   ` Wang, Jian J
2019-10-15  0:26 ` [Patch v2 09/11] CryptoPkg IntrinsicLib: Make _fltused always be used Liming Gao
2019-10-15  9:30   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-16  1:10   ` Wang, Jian J
2019-10-15  0:26 ` [Patch v2 10/11] EmulatorPkg: Enable CLANG9 tool chain Liming Gao
2019-10-16  9:32   ` [edk2-devel] " Ni, Ray
2019-10-17  3:31     ` Liming Gao
2019-10-17  5:21       ` Ni, Ray [this message]
2019-10-15  0:26 ` [Patch v2 11/11] OvmfPkg: " Liming Gao
2019-10-15  7:36 ` [edk2-devel] [Patch v2 00/11] New Cross OS tool chain CLANG9 Laszlo Ersek
2019-10-16  0:55   ` Liming Gao
2019-10-16  9:19 ` Bob Feng
2019-10-17  2:15   ` Liming Gao

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=734D49CCEBEEF84792F5B80ED585239D5C325901@SHSMSX104.ccr.corp.intel.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