From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Basetools fail without error message due to PCD type differs in architecture.
To: devel@edk2.groups.io
From: "Lin, Derek (HPS SW)" <derek.lin2@hpe.com>
X-Originating-Location: Taipei, Taipei City, TW (1.164.226.77)
X-Originating-Platform: Windows Chrome 80
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Sun, 05 Apr 2020 19:55:18 -0700
Message-ID: <tBVh.1586141718229466021.XBeY@groups.io>
Content-Type: multipart/alternative; boundary="eOsBwViEqaLUMcVj6CLN"

--eOsBwViEqaLUMcVj6CLN
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

We've found a Basetool issue.
When a PCD is FixAtBuild at IA32 and Dynamic is at X64, there is no error =
message in this situation and it's very difficult to find the root cause.

Here's example to see the issue:
https://github.com/howdou/edk2/commit/333c5f33adc652308355ec100f7f385d5523=
92fa

I think it is not allowed to have FixAtBuild at IA32 and Dynamic at X64. B=
aseTool should have an error message for this.

--eOsBwViEqaLUMcVj6CLN
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

We've found a Basetool issue.&nbsp;<br />When a PCD is FixAtBuild at IA32 a=
nd Dynamic is at X64, there is no error message in this situation and it's =
very difficult to find the root cause.<br /><br />Here's example to see the=
 issue:<br /><a href=3D"https://github.com/howdou/edk2/commit/333c5f33adc65=
2308355ec100f7f385d552392fa">https://github.com/howdou/edk2/commit/333c5f33=
adc652308355ec100f7f385d552392fa</a><br /><br />I think it is not allowed t=
o have FixAtBuild at IA32 and Dynamic at X64. BaseTool should have an error=
 message for this.

--eOsBwViEqaLUMcVj6CLN--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (NAM02-CY1-obe.outbound.protection.outlook.com [40.107.76.130])
 by mx.groups.io with SMTP id smtpd.web12.252.1586296090752699536
 for <devel@edk2.groups.io>;
 Tue, 07 Apr 2020 14:48:10 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@microsoft.com header.s=selector2 header.b=fPcboe/t;
 spf=pass (domain: microsoft.com, ip: 40.107.76.130, mailfrom: bret.barkelew@microsoft.com)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=DEu2RtobPwEvMaPF6CdOmdHGeZXTIERIbrSpoaje/5dYhlIW3x7yL3nz4nXg9FjJnyWHAz/wadSSuD17fo47PFJ9uevwF1+zWkwwBl2S70ixzcL3aynR/4dj/z25LhtO+0yxTUOIPGtnnSR+8mxvPkcsJ9CHYLtLbMyJbiJN3yWfPlThZaYfK7oEi5nD8KAcSjHnTwpVkmjaTeM7oIyCiRzaKqkmxkY8QZ3Id4iavRnW+VqLRcGVN/DJwvU/x6EvIFATnRuGHNAdcPGaqBQWIRgqNMhkoXPUnqDwIDS+YFDl3KrLmWLiqgbPhqnJ2MeKF3oYGUuooZ+MGGJi6+DTCA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=HQ9HWMPRSD6+3KOQt6Jmcbx54LMkMy66JwRq+5UWoRs=;
 b=GhMxAgwTgYKtWh4cerunfjPlaAJDlwHCnQWD0zNBHlTcDCOlZpL9Q5M1OvTdjMHDQNX8s2eb8twT/47TdFCrnIZdTok0QqDSzcehxcEW5S5zsFA8b6MG/Kp1Luf6bQ4LqJNdGK0RxrARhxmTlaJ/b1nFayk1mr5hw7wgeHV+MePhZYrt0nOvWmmKA83t6FDu359jenoGEw9AXAMaK2tHZUBNgUTpvaf2WZacajk3eN4p8i96d8la7jkqOzwjySuKy4/uTyKM7QXdt2UGyTAMnuHmXHH2vOd5ErppOYPRj1a5Hxba1B7OpGOs5HabIi63QnWY4gPf3W+74WzQdSxZgg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
 smtp.mailfrom=microsoft.com; dmarc=pass action=none
 header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=selector2;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=HQ9HWMPRSD6+3KOQt6Jmcbx54LMkMy66JwRq+5UWoRs=;
 b=fPcboe/tqigKm9YyouaXwmYqeQ+/czlHXqbajTkdDgXJdkckDuiz5r17n8l8xpyf+KQj8aFNcI54kojA0A317Ca2xFSAE70bodXFd+1vf8lTlVfHFfQT8t+PXNa7RL0nBVYisOoAB2STROSg15QC4ntOT6fvUW0lVUfIBht03Rg=
Received: from CY4PR21MB0743.namprd21.prod.outlook.com (2603:10b6:903:b2::9)
 by CY4PR21MB0776.namprd21.prod.outlook.com (2603:10b6:903:b8::22) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.2; Tue, 7 Apr
 2020 21:48:09 +0000
Received: from CY4PR21MB0743.namprd21.prod.outlook.com
 ([fe80::90d:10d9:c5bc:5318]) by CY4PR21MB0743.namprd21.prod.outlook.com
 ([fe80::90d:10d9:c5bc:5318%12]) with mapi id 15.20.2921.000; Tue, 7 Apr 2020
 21:48:09 +0000
From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>, "derek.lin2@hpe.com"
	<derek.lin2@hpe.com>
Subject: Re: [EXTERNAL] [edk2-devel] Basetools fail without error message due to PCD type differs in architecture.
Thread-Topic: [EXTERNAL] [edk2-devel] Basetools fail without error message due
 to PCD type differs in architecture.
Thread-Index: AQHWC77PstnNCCHZj0qxPlN7wIbHu6huNKxx
Date: Tue, 7 Apr 2020 21:48:09 +0000
Message-ID: 
 <CY4PR21MB0743481A4EF4593F059B4ED9EFC30@CY4PR21MB0743.namprd21.prod.outlook.com>
References: <tBVh.1586141718229466021.XBeY@groups.io>
In-Reply-To: <tBVh.1586141718229466021.XBeY@groups.io>
Accept-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
msip_labels: 
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-04-07T21:47:06.5120318Z;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Privileged
authentication-results: spf=none (sender IP is )
 smtp.mailfrom=Bret.Barkelew@microsoft.com; 
x-originating-ip: [71.212.145.195]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: f6b3735c-12c1-4c28-c2e5-08d7db3d5cea
x-ms-traffictypediagnostic: CY4PR21MB0776:
x-microsoft-antispam-prvs: 
 <CY4PR21MB0776D946E67623F1C88177DCEFC30@CY4PR21MB0776.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:1265;
x-forefront-prvs: 036614DD9C
x-forefront-antispam-report: 
 CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:CY4PR21MB0743.namprd21.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:(10019020)(4636009)(396003)(366004)(39850400004)(136003)(346002)(376002)(66556008)(52536014)(64756008)(86362001)(82950400001)(82960400001)(66476007)(8676002)(316002)(53546011)(110136005)(99936003)(8990500004)(6506007)(66946007)(9686003)(66616009)(55016002)(66446008)(76116006)(81156014)(76236002)(81166006)(478600001)(10290500003)(26005)(15650500001)(91956017)(2906002)(33656002)(71200400001)(8936002)(186003)(7696005)(5660300002)(966005);DIR:OUT;SFP:1102;
received-spf: None (protection.outlook.com: microsoft.com does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 
 6zU83jfD/DSVqjGE0F2VV7Veo82hppW5I0woEkKaE7PuWeK2neEIj0N5MxePBGqM0ZZBJHqEysuvJ+S08tWLO1Pu6joWRF07z5Up6YSD5GFB2OW3DyFltrRsKys3gLyO1UDKgPz7/kHRWsoRSYj6AKrdFVqmyWGMSfp/a1yhG2ca6j26ZBo7i2iU8zP9dV1H3seXnfMorKCBymcil6Zn/jNlYYb0aCBR/0OV4KMukNNvCuxMCkNXdc+b+a9+Wg6o4jA6ihdbYj86vdWVMdAcUjnQHh2Ft2pzYjsGWWabGN0pFt6znddlLdZWgSmoOcgb2laL7nSWQze2ZFvBtBTQP66hZ4SCdVUvfx8Q4i1k5jKBfEYZifCoCiQ1ijfWc2vng1TpCfsleqHVxNk/pao3PZljfUy2Qu8N3g1WPRFWPEHnQgRlk3AMBD390VNMmbSZLxToWHXdh5q9CKLl7L5BlktklqgR9sejTVVCt90GEP2/B9AiRSmXqvFPKIcwQjZuXNDjy/DiEo8fxy2ok1QHtg==
x-ms-exchange-antispam-messagedata: 
 /z84t2CRM08Qwrdl/wdXO+5bMgd8ZFveCRhz9mcOr71IBXOrZQvqekYPmAa4UU74zZdQ9dG4cap5YVEyL5ab83iaX7gt1xg3u58+sQ1bInlm4THI8kCEJJh40vvtclmtHH+LGRHKoiHQa/ivBQ14Rg==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f6b3735c-12c1-4c28-c2e5-08d7db3d5cea
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2020 21:48:09.2882
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hToEor8lOtMUY1wjE4OYDsNYATid1X7w71UH5XtxC+apAtIhwaKoONaZLu37s332NF62xaFqRljVuftL3kquEQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0776
X-Groupsio-MsgNum: 57031
Content-Language: en-US
Content-Type: multipart/related;
	boundary="_004_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_";
	type="multipart/alternative"

--_004_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_
Content-Type: multipart/alternative;
	boundary="_000_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_"

--_000_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

This seems like a legitimate configuration. I don=92t know that it should b=
e considered an error. A warning, maybe.

This is also what the build report is perfect for finding. Did you check t=
he PCD build report when debugging?

- Bret

From: Lin, Derek (HPS SW) via groups.io<mailto:derek.lin2=3Dhpe.com@groups=
.io>
Sent: Sunday, April 5, 2020 7:55 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [EXTERNAL] [edk2-devel] Basetools fail without error message due =
to PCD type differs in architecture.

We've found a Basetool issue.
When a PCD is FixAtBuild at IA32 and Dynamic is at X64, there is no error =
message in this situation and it's very difficult to find the root cause.

Here's example to see the issue:
https://github.com/howdou/edk2/commit/333c5f33adc652308355ec100f7f385d5523=
92fa<https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgi=
thub.com%2Fhowdou%2Fedk2%2Fcommit%2F333c5f33adc652308355ec100f7f385d552392f=
a&data=3D02%7C01%7Cbret.barkelew%40microsoft.com%7Cffb03103e6ea44f2983d08d7=
d9d5f14d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637217385209311719&sd=
ata=3DNARbUbs0zdooQRcLakblGydppgYFoxm1BBNhm4Ap4Ek%3D&reserved=3D0>

I think it is not allowed to have FixAtBuild at IA32 and Dynamic at X64. B=
aseTool should have an error message for this.



--_000_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-=
1252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">This seems like a legitimate configuration. I don=
=92t know that it should be considered an error. A warning, maybe.</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is also what the build report is perfect for f=
inding. Did you check the PCD build report when debugging?</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">- Bret</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"mso-element:para-border-div;border:none;border-top:solid #E1=
E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class=3D"MsoNormal" style=3D"border:none;padding:0in"><b>From: </b><a h=
ref=3D"mailto:derek.lin2=3Dhpe.com@groups.io">Lin, Derek (HPS SW) via group=
s.io</a><br>
<b>Sent: </b>Sunday, April 5, 2020 7:55 PM<br>
<b>To: </b><a href=3D"mailto:devel@edk2.groups.io">devel@edk2.groups.io</a=
><br>
<b>Subject: </b>[EXTERNAL] [edk2-devel] Basetools fail without error messa=
ge due to PCD type differs in architecture.</p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We've found a Basetool issue.&nbsp;<br>
When a PCD is FixAtBuild at IA32 and Dynamic is at X64, there is no error =
message in this situation and it's very difficult to find the root cause.<b=
r>
<br>
Here's example to see the issue:<br>
<a href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%=
2F%2Fgithub.com%2Fhowdou%2Fedk2%2Fcommit%2F333c5f33adc652308355ec100f7f385d=
552392fa&amp;data=3D02%7C01%7Cbret.barkelew%40microsoft.com%7Cffb03103e6ea4=
4f2983d08d7d9d5f14d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6372173852=
09311719&amp;sdata=3DNARbUbs0zdooQRcLakblGydppgYFoxm1BBNhm4Ap4Ek%3D&amp;res=
erved=3D0">https://github.com/howdou/edk2/commit/333c5f33adc652308355ec100f=
7f385d552392fa</a><br>
<br>
I think it is not allowed to have FixAtBuild at IA32 and Dynamic at X64. B=
aseTool should have an error message for this.
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_--

--_004_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_
Content-Type: image/png; name="CAF964A0152545AF8C2BF291DCCC1423.png"
Content-Description: CAF964A0152545AF8C2BF291DCCC1423.png
Content-Disposition: inline; filename="CAF964A0152545AF8C2BF291DCCC1423.png";
	size=140; creation-date="Tue, 07 Apr 2020 21:48:07 GMT";
	modification-date="Tue, 07 Apr 2020 21:48:07 GMT"
Content-ID: <image002.png@01D60CEB.8D152770>
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAsQAAAABCAYAAADZ77itAAAAAXNSR0IArs4c6QAAAARnQU1BAACx
jwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAhSURBVEhL7cMBDQAACAMg+5cygQkeRoMIG9WT
VVXVn7MHYi5moJeByLMAAAAASUVORK5CYII=

--_004_CY4PR21MB0743481A4EF4593F059B4ED9EFC30CY4PR21MB0743namp_--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mx0b-002e3701.pphosted.com (mx0b-002e3701.pphosted.com [148.163.143.35])
 by mx.groups.io with SMTP id smtpd.web10.4709.1586313656103609452
 for <devel@edk2.groups.io>;
 Tue, 07 Apr 2020 19:40:56 -0700
Authentication-Results: mx.groups.io;
 dkim=missing; spf=pass (domain: hpe.com, ip: 148.163.143.35, mailfrom: prvs=036735f001=derek.lin2@hpe.com)
Received: from pps.filterd (m0150244.ppops.net [127.0.0.1])
	by mx0b-002e3701.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 0382bw18029209
	for <devel@edk2.groups.io>; Wed, 8 Apr 2020 02:40:55 GMT
Received: from g4t3427.houston.hpe.com (g4t3427.houston.hpe.com [15.241.140.73])
	by mx0b-002e3701.pphosted.com with ESMTP id 3091pd9gs5-1
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
	for <devel@edk2.groups.io>; Wed, 08 Apr 2020 02:40:55 +0000
Received: from G4W10205.americas.hpqcorp.net (g4w10205.houston.hpecorp.net [16.207.82.15])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
	(No client certificate requested)
	by g4t3427.houston.hpe.com (Postfix) with ESMTPS id 910C457
	for <devel@edk2.groups.io>; Wed,  8 Apr 2020 02:40:54 +0000 (UTC)
Received: from G4W10204.americas.hpqcorp.net (2002:10cf:5210::10cf:5210) by
 G4W10205.americas.hpqcorp.net (2002:10cf:520f::10cf:520f) with Microsoft SMTP
 Server (TLS) id 15.0.1497.2; Wed, 8 Apr 2020 02:40:54 +0000
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (15.241.52.10) by
 G4W10204.americas.hpqcorp.net (16.207.82.16) with Microsoft SMTP Server (TLS)
 id 15.0.1497.2 via Frontend Transport; Wed, 8 Apr 2020 02:40:54 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=QxH0i9kmTwAhVV0pQLpwn8IHT3RQaGOVgvFyPMcliMX5RZqIA4Cw1+SzV8Anuthx3FuoEfw7+zc6wSxF5347M0pjx/bgisS38mwIKVSQjo961gZWOLAVAsGI7bxPEq9phttZws74Icq6c4cfRea8QLCmOhsCrxGt7otv7CNOvhQxssqq1Pa7ch60HhzC1dT9MbtwZLzKJx9scLfZ9HyQnd28QVXbauWXyTB2WhaLtBHIXpOd+WygpvV+Lyzo8VuttckzeVOCBt/T17bENZATnxeKYo926OE0Etjg/LHgaMbcW+HV57GYOEgGon5loXWSgqjaBryHgv9rpMuloKf8uQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=DR+TxEixeIuomVUBr95z0b7hF8fYlIP8mVnGMJfCpu0=;
 b=RBm2V+Kd4m+avtW5199YptMQgRAN6uSztO+kjBEZUxOH79tx3OCdDtRceVjUM44RdQGiUeSgxYG8tpo2Zyf0awQp7XhP8gDeViVzNZmdupaua7gQePscwFUjwSYXCgNx/1RzzoLAQex0SsByEhuAVEr+VzlZcVONwvkA7zakLUl5xN2tLKO76lD4g2IBfujs5Sz5L+UlHXGliK471l/CM8IZ8RUYXqIC1cBEkPRE1PEP1LDxDwF3FjMCnDym8+koPcbj/v3xsmeNZmYOW4tjLgmpTDeUbuI/jtjJW4KaS9ljZIRolDny77D5f1nQU4Ie9wcf1SN+7QXYWCC2MvHFdA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
 smtp.mailfrom=hpe.com; dmarc=pass action=none header.from=hpe.com; dkim=pass
 header.d=hpe.com; arc=none
Received: from DF4PR8401MB0955.NAMPRD84.PROD.OUTLOOK.COM
 (2a01:111:e400:760f::11) by DF4PR8401MB0876.NAMPRD84.PROD.OUTLOOK.COM
 (2a01:111:e400:760e::17) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15; Wed, 8 Apr
 2020 02:40:51 +0000
Received: from DF4PR8401MB0955.NAMPRD84.PROD.OUTLOOK.COM
 ([fe80::441e:61a:d8e9:f204]) by DF4PR8401MB0955.NAMPRD84.PROD.OUTLOOK.COM
 ([fe80::441e:61a:d8e9:f204%10]) with mapi id 15.20.2900.015; Wed, 8 Apr 2020
 02:40:51 +0000
From: "Lin, Derek (HPS SW)" <derek.lin2@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
        "bret.barkelew@microsoft.com" <bret.barkelew@microsoft.com>
Thread-Topic: [EXTERNAL] [edk2-devel] Basetools fail without error message due
 to PCD type differs in architecture.
Thread-Index: AQHWC77VhtNEpxXJS0O7ez3pXmML2ahuNPaAgABJkIA=
Date: Wed, 8 Apr 2020 02:40:51 +0000
Message-ID: <DF4PR8401MB09557F87A1A9D7532961064DC2C00@DF4PR8401MB0955.NAMPRD84.PROD.OUTLOOK.COM>
References: <tBVh.1586141718229466021.XBeY@groups.io>
 <CY4PR21MB0743481A4EF4593F059B4ED9EFC30@CY4PR21MB0743.namprd21.prod.outlook.com>
In-Reply-To: <CY4PR21MB0743481A4EF4593F059B4ED9EFC30@CY4PR21MB0743.namprd21.prod.outlook.com>
Accept-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [1.171.104.224]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a57c1ec3-3961-423a-92bb-08d7db6640f2
x-ms-traffictypediagnostic: DF4PR8401MB0876:
x-microsoft-antispam-prvs: <DF4PR8401MB087690EC7C032314760362DDC2C00@DF4PR8401MB0876.NAMPRD84.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:1107;
x-forefront-prvs: 0367A50BB1
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DF4PR8401MB0955.NAMPRD84.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFTY:;SFS:(10019020)(39860400002)(136003)(366004)(346002)(376002)(396003)(55016002)(186003)(66556008)(66446008)(7696005)(66946007)(66476007)(64756008)(9686003)(26005)(52536014)(86362001)(15650500001)(316002)(76116006)(2906002)(6506007)(966005)(53546011)(478600001)(110136005)(33656002)(8676002)(5660300002)(81156014)(76236002)(9326002)(81166006)(71200400001)(8936002);DIR:OUT;SFP:1102;
received-spf: None (protection.outlook.com: hpe.com does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: mELFrZjuu1ko+geucnpjkDgY93jmOv7qZuSpK0usrQUdu9vdXyKZgwWi0TjJsMexI0xB37CeXdOAG0PWCw4PMUYyBvrfgJ6XIBuiROhkYYY+JzpR+Gwzy3knJAZTQ38qakVBu+J4MPtsa4fnQlzPCQjE+rO+IsBFgTRI5NoKFOXpLTRAgTulTwhq7l7cuAEjHFjDA09XtYtaOgemvtjsYkLj9jH5wMJHMwadI/bc2tI1UoZWhacpVNX5p3F6frnhi5eKHa28wONrxI2LonwsHBqCciAhPKIx9T4KmRBNJvHedWommhLUm4Nm/Vyf0YyDUBUIIrrok/DkPYklSvPsaFEhRxp2xJWSr1m9OQ1z9GU9EqJ8z9MVAgF16PTsRCc6brFOdAVIsEvHB5/UJDWE3SVOPj8IEhkrQB5sryRAm1ujHtaJv6X+s6rkNaCW2akuY6anoSt6i9yZu/AUZX3TlLS0PxRZX66k+bVU36q8xIQHfHT4MBvHaj9BGgzIhCAbWPUyFQ0rZLYIpv1s7FrSyA==
x-ms-exchange-antispam-messagedata: E1DPevBG9JNrklvYIWHryQvSfcDfKQaBy8u22YV61wZd7YzfhNgdBfQJVGyVU5VgidSx0xc0mgyLhC06cGSj7UCHDtN4O/VHPq9GMf/2+KBp2RD1c77Kprb4m1GfHdducQcsFi+fn6YUgQqILgmJkg==
x-ms-exchange-transport-forked: True
X-MS-Exchange-CrossTenant-Network-Message-Id: a57c1ec3-3961-423a-92bb-08d7db6640f2
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2020 02:40:51.7681
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: wMnmosansbKwEeEQgpytw88ZE2F40Tg4C5r9nANNhWpkHdF2K4ec6rGrZO2QSea4u1oM9kGgtov5bRmpqIrXdw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DF4PR8401MB0876
X-OriginatorOrg: hpe.com
X-Proofpoint-UnRewURL: 12 URL's were un-rewritten
MIME-Version: 1.0
X-HPE-SCL: -1
Subject: Re: [edk2-devel] Basetools fail without error message due to PCD type differs in architecture.
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138,18.0.676
 definitions=2020-04-07_10:2020-04-07,2020-04-07 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxlogscore=687
 lowpriorityscore=0 clxscore=1015 mlxscore=0 spamscore=0 phishscore=0
 malwarescore=0 impostorscore=0 bulkscore=0 adultscore=0 suspectscore=0
 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.12.0-2003020000 definitions=main-2004080015
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_DF4PR8401MB09557F87A1A9D7532961064DC2C00DF4PR8401MB0955_"

--_000_DF4PR8401MB09557F87A1A9D7532961064DC2C00DF4PR8401MB0955_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Bret,

Thanks for your feedback. I'm very sorry that I didn't describe it clearly=
.

The Basetools just "crash" in the configuration. The Basetools crash witho=
ut any information, then build stops.
I've looked into the BaseTools code, the python code crash, during the gen=
eration of PCD database for IA32.


I'm not sure if the PCD spec allows different PCD type in different archit=
ectures.
If the spec allows it, the build needs to be fixed and make sure it works.=
 I remember the dynamic PCD database carry from PEI to DXE. And I don't thi=
nk that work if PEI is FixedAtBuild while DXE is Dyanamic.

In my opinion, this configuration should come to a build failure. And defi=
ne the error in PCD spec.

Thanks,
Derek

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Bret=
 Barkelew via groups.io
Sent: Wednesday, April 8, 2020 5:48 AM
To: devel@edk2.groups.io; Lin, Derek (HPS SW) <derek.lin2@hpe.com>
Subject: Re: [EXTERNAL] [edk2-devel] Basetools fail without error message =
due to PCD type differs in architecture.

This seems like a legitimate configuration. I don't know that it should be=
 considered an error. A warning, maybe.

This is also what the build report is perfect for finding. Did you check t=
he PCD build report when debugging?

- Bret

From: Lin, Derek (HPS SW) via groups.io<mailto:derek.lin2=3Dhpe.com@groups=
.io>
Sent: Sunday, April 5, 2020 7:55 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [EXTERNAL] [edk2-devel] Basetools fail without error message due =
to PCD type differs in architecture.

We've found a Basetool issue.
When a PCD is FixAtBuild at IA32 and Dynamic is at X64, there is no error =
message in this situation and it's very difficult to find the root cause.

Here's example to see the issue:
https://github.com/howdou/edk2/commit/333c5f33adc652308355ec100f7f385d5523=
92fa<https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgi=
thub.com%2Fhowdou%2Fedk2%2Fcommit%2F333c5f33adc652308355ec100f7f385d552392f=
a&data=3D02%7C01%7Cbret.barkelew%40microsoft.com%7Cffb03103e6ea44f2983d08d7=
d9d5f14d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637217385209311719&sd=
ata=3DNARbUbs0zdooQRcLakblGydppgYFoxm1BBNhm4Ap4Ek%3D&reserved=3D0>

I think it is not allowed to have FixAtBuild at IA32 and Dynamic at X64. B=
aseTool should have an error message for this.



--_000_DF4PR8401MB09557F87A1A9D7532961064DC2C00DF4PR8401MB0955_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii=
">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:PMingLiU;
	panose-1:2 2 3 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@PMingLiU";
	panose-1:2 2 3 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Bret,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your feedb=
ack. I&#8217;m very sorry that I didn&#8217;t describe it clearly.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The Basetools just &#=
8220;crash&#8221; in the configuration. The Basetools crash without any inf=
ormation, then build stops.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I&#8217;ve looked int=
o the BaseTools code, the python code crash, during the generation of PCD d=
atabase for IA32.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I&#8217;m not sure if=
 the PCD spec allows different PCD type in different architectures.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If the spec allows it=
, the build needs to be fixed and make sure it works. I remember the dynami=
c PCD database carry from PEI to DXE. And I don&#8217;t think that work if =
PEI is FixedAtBuild while DXE is Dyanamic.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In my opinion, this c=
onfiguration should come to a build failure. And define the error in PCD sp=
ec.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Derek<o:p></o:p></spa=
n></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in=
 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> devel@edk2.groups.io [mailto:devel@edk=
2.groups.io]
<b>On Behalf Of </b>Bret Barkelew via groups.io<br>
<b>Sent:</b> Wednesday, April 8, 2020 5:48 AM<br>
<b>To:</b> devel@edk2.groups.io; Lin, Derek (HPS SW) &lt;derek.lin2@hpe.co=
m&gt;<br>
<b>Subject:</b> Re: [EXTERNAL] [edk2-devel] Basetools fail without error m=
essage due to PCD type differs in architecture.<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This seems like a legitimate configuration. I don&#=
8217;t know that it should be considered an error. A warning, maybe.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is also what the build report is perfect for f=
inding. Did you check the PCD build report when debugging?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">- Bret<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in=
 0in 0in">
<p class=3D"MsoNormal"><b>From: </b><a href=3D"mailto:derek.lin2=3Dhpe.com=
@groups.io">Lin, Derek (HPS SW) via groups.io</a><br>
<b>Sent: </b>Sunday, April 5, 2020 7:55 PM<br>
<b>To: </b><a href=3D"mailto:devel@edk2.groups.io">devel@edk2.groups.io</a=
><br>
<b>Subject: </b>[EXTERNAL] [edk2-devel] Basetools fail without error messa=
ge due to PCD type differs in architecture.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We've found a Basetool issue.&nbsp;<br>
When a PCD is FixAtBuild at IA32 and Dynamic is at X64, there is no error =
message in this situation and it's very difficult to find the root cause.<b=
r>
<br>
Here's example to see the issue:<br>
<a href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%=
2F%2Fgithub.com%2Fhowdou%2Fedk2%2Fcommit%2F333c5f33adc652308355ec100f7f385d=
552392fa&data=3D02%7C01%7Cbret.barkelew%40microsoft.com%7Cffb03103e6ea44f29=
83d08d7d9d5f14d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63721738520931=
1719&sdata=3DNARbUbs0zdooQRcLakblGydppgYFoxm1BBNhm4Ap4Ek%3D&reserved=3D0">h=
ttps://github.com/howdou/edk2/commit/333c5f33adc652308355ec100f7f385d552392=
fa</a><br>
<br>
I think it is not allowed to have FixAtBuild at IA32 and Dynamic at X64. B=
aseTool should have an error message for this.
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_DF4PR8401MB09557F87A1A9D7532961064DC2C00DF4PR8401MB0955_--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (NAM12-BN8-obe.outbound.protection.outlook.com [40.107.237.128])
 by mx.groups.io with SMTP id smtpd.web10.5657.1586319112474342435
 for <devel@edk2.groups.io>;
 Tue, 07 Apr 2020 21:11:53 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@microsoft.com header.s=selector2 header.b=GXAkbUfJ;
 spf=pass (domain: microsoft.com, ip: 40.107.237.128, mailfrom: bret.barkelew@microsoft.com)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=BkBG8F+N9NuImcM2KdTQJedjZq/tHWuugMn9srj1eiJm7NbTQud9HlqHGYRmb1OlIJEgPUVsNYbLjyCeI3V38u/Bxku1gy6zQYsQxDbnHWUU6lG/qjqCg9JZdprqt3B1h0lrdxpcw8CO7St1NBVjVfhjo87UHgv1BuX28vow41KN6i/nx9mG1xoISZvJmTzYtmeAtDcz7CWskacxsB7sVK3i0etEt4t+Fu4XMQW3DpOnfrsLanECJ3slX/cZw7yuCDjZfJTmpZP39WJe6AZlP/VtOpJI4BvZ9gEsrHZG48pEmttyR2dE2WL0TUGVVCbhFAJi/eV2nNX3JWyMfDMqOQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=Gs8H7pLR1w0hs7KQmAg9sFL6Ec4AnF/7Dlj31LTGtS4=;
 b=NMv9CD1n7Ec04j0gghzBa9KbkbxacMBcjrTiN8KQlFoWWe+u12ubW7mw0OugWdDq6m1N86AJenYhYF1Yi4F4th3ORPhR78w8+BbCeTwp9EDkkKPl5UMmSnpbuqW3p7zrjzUhvDYbgprUHg41crgv46KMnmcoqWg3jhJBH41bOaJooijkWw2i8sFLH6iA+wWLroc4pZ90xnXC4Vm26lLcWe9+WvZIEqyTMcMhF7GIDkoGc1mfEJXSHU3RYlw3pGSCzq7Rj0DUDSHz67+jyeTjRqMtj+DYlyiWRJtTlvPpVM8VOdq2ZyZh7yldnwlcLxxEEwk3u8tcowqBxEO1zO5RgA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
 smtp.mailfrom=microsoft.com; dmarc=pass action=none
 header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=selector2;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=Gs8H7pLR1w0hs7KQmAg9sFL6Ec4AnF/7Dlj31LTGtS4=;
 b=GXAkbUfJtvD3j4PLvPs/EUshAvmRKkCnCkheAMUubMsgIBAj39kMRR/8Zhqk1S/g3XGmQqiMl2cW0L9ii7DqFm+7k8a/IW1vVlUrPB6bI4M4QEWReVe3ok71OQxsbda1RhrrYT71w6P/yr/3AlpMaD6QZsWAcd/taddZ8yZknSg=
Received: from CY4PR21MB0743.namprd21.prod.outlook.com (2603:10b6:903:b2::9)
 by CY4PR21MB0773.namprd21.prod.outlook.com (2603:10b6:903:b8::19) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.2; Wed, 8 Apr
 2020 04:11:50 +0000
Received: from CY4PR21MB0743.namprd21.prod.outlook.com
 ([fe80::90d:10d9:c5bc:5318]) by CY4PR21MB0743.namprd21.prod.outlook.com
 ([fe80::90d:10d9:c5bc:5318%12]) with mapi id 15.20.2921.009; Wed, 8 Apr 2020
 04:11:50 +0000
From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "Lin, Derek (HPS SW)" <derek.lin2@hpe.com>, "devel@edk2.groups.io"
	<devel@edk2.groups.io>
Subject: Re: [edk2-devel] Basetools fail without error message due to PCD type differs in architecture.
Thread-Topic: [edk2-devel] Basetools fail without error message due to PCD
 type differs in architecture.
Thread-Index: AQHWDU8iUFiR9f4mh0qhmFhpdRb6XahunNa+
Date: Wed, 8 Apr 2020 04:11:50 +0000
Message-ID: 
 <CY4PR21MB0743989EE27B2EA630EE4187EFC00@CY4PR21MB0743.namprd21.prod.outlook.com>
References: <tBVh.1586141718229466021.XBeY@groups.io>
 <CY4PR21MB0743481A4EF4593F059B4ED9EFC30@CY4PR21MB0743.namprd21.prod.outlook.com>,<DF4PR8401MB09557F87A1A9D7532961064DC2C00@DF4PR8401MB0955.NAMPRD84.PROD.OUTLOOK.COM>
In-Reply-To: 
 <DF4PR8401MB09557F87A1A9D7532961064DC2C00@DF4PR8401MB0955.NAMPRD84.PROD.OUTLOOK.COM>
Accept-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
msip_labels: 
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-04-08T04:11:07.2644587Z;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Privileged
authentication-results: spf=none (sender IP is )
 smtp.mailfrom=Bret.Barkelew@microsoft.com; 
x-originating-ip: [71.212.145.195]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: dd256cad-2c71-45aa-714c-08d7db72f6c3
x-ms-traffictypediagnostic: CY4PR21MB0773:
x-microsoft-antispam-prvs: 
 <CY4PR21MB0773EC34E6D6620B757E39F5EFC00@CY4PR21MB0773.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0367A50BB1
x-forefront-antispam-report: 
 CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:CY4PR21MB0743.namprd21.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:(10019020)(4636009)(366004)(396003)(346002)(376002)(136003)(39860400002)(33656002)(9686003)(26005)(5660300002)(81156014)(71200400001)(110136005)(8936002)(76236002)(82950400001)(81166007)(82960400001)(316002)(296002)(8676002)(99936003)(55016002)(966005)(2906002)(15650500001)(52536014)(64756008)(53546011)(10290500003)(6506007)(86362001)(76116006)(7696005)(186003)(66446008)(66556008)(66616009)(66946007)(8990500004)(478600001)(66476007);DIR:OUT;SFP:1102;
received-spf: None (protection.outlook.com: microsoft.com does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 
 y0oVlQEindypM96NaM/CaYJhnPkDQ1FbYzRd9xSf2YxluiNzRar+IxGDGKhIovnljMVnu9h+GCBGOaA8YcdxlP/JVJLRYPFPTOalBO1DOc+0BVQ4wygWQu9NgqwrAucb0eWEfPZR/CrI9KmxvrD2MbCFVmlimJMqToYmkGcyeWFqmgpvRxTeBWma+9+nCl8rqAaCGdwWF6yL9fePdTgcXJRj5ZGRt7tB8EQAdVYfkXmCSw5vW+h522ho0WeBf4ktMvRM8pERz+CffNJhOMJEwPG2El2zE/s8GHg/s4RA6hcgQ4fF4U4SdppOIQOjg1PvMqCjaqP/gOKG3ClFWylN4AsOhaW3OkDB2/4QD2xrvUbXkAtoZ3r5BGh9baYmoHt7N2QWgFwXRQJvUiFqz+zI92R3Sv2izgW1e4AeeHOdlCYdltGKRQXD5Px1/OM3URYNop6A7pKr3BUBfVa5Z6AMxCmzSDjCNXh75qQGiHTbjCw9eYl5SgkE1c2ZZio2/ESgMR9dMAGNx3IcdrkgoDa3TA==
x-ms-exchange-antispam-messagedata: 
 g1I0xMak/8+s55wR+SUMgE3A4noUFX3U9AGBDhw3EPybAQCnNMBvIaD/LThd/eSUFtoTSjaj0vmGmNPFDHP9Mt4YfkEsvCYJ9ZXvNC9LcTrsoBcDUVKaYYlPYSDHuyGMAEMElSoREK69zjz5CJhoAQ==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: dd256cad-2c71-45aa-714c-08d7db72f6c3
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2020 04:11:50.8173
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eRlTXZvS2LVTjNKixeReMalaIVYV9EF01dBD7g7pxYeuln1mrWUyK5NygvmDEPuH3iaoXAqTI0Gj8IVDMAFdZQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0773
X-Groupsio-MsgNum: 57047
Content-Language: en-US
Content-Type: multipart/related;
	boundary="_004_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_";
	type="multipart/alternative"

--_004_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_
Content-Type: multipart/alternative;
	boundary="_000_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_"

--_000_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

AH! Okay. I would agree that a build crash without an actionable error is s=
omething we want to fix.

- Bret

From: Lin, Derek (HPS SW)<mailto:derek.lin2@hpe.com>
Sent: Tuesday, April 7, 2020 7:40 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Bret Barkelew<mailt=
o:Bret.Barkelew@microsoft.com>
Subject: RE: [edk2-devel] Basetools fail without error message due to PCD =
type differs in architecture.

Hi Bret,

Thanks for your feedback. I=92m very sorry that I didn=92t describe it cle=
arly.

The Basetools just =93crash=94 in the configuration. The Basetools crash w=
ithout any information, then build stops.
I=92ve looked into the BaseTools code, the python code crash, during the g=
eneration of PCD database for IA32.


I=92m not sure if the PCD spec allows different PCD type in different arch=
itectures.
If the spec allows it, the build needs to be fixed and make sure it works.=
 I remember the dynamic PCD database carry from PEI to DXE. And I don=92t t=
hink that work if PEI is FixedAtBuild while DXE is Dyanamic.

In my opinion, this configuration should come to a build failure. And defi=
ne the error in PCD spec.

Thanks,
Derek

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Bret=
 Barkelew via groups.io
Sent: Wednesday, April 8, 2020 5:48 AM
To: devel@edk2.groups.io; Lin, Derek (HPS SW) <derek.lin2@hpe.com>
Subject: Re: [EXTERNAL] [edk2-devel] Basetools fail without error message =
due to PCD type differs in architecture.

This seems like a legitimate configuration. I don=92t know that it should =
be considered an error. A warning, maybe.

This is also what the build report is perfect for finding. Did you check t=
he PCD build report when debugging?

- Bret

From: Lin, Derek (HPS SW) via groups.io<mailto:derek.lin2=3Dhpe.com@groups=
.io>
Sent: Sunday, April 5, 2020 7:55 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [EXTERNAL] [edk2-devel] Basetools fail without error message due =
to PCD type differs in architecture.

We've found a Basetool issue.
When a PCD is FixAtBuild at IA32 and Dynamic is at X64, there is no error =
message in this situation and it's very difficult to find the root cause.

Here's example to see the issue:
https://github.com/howdou/edk2/commit/333c5f33adc652308355ec100f7f385d5523=
92fa<https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fur=
ldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__nam06.safelinks.protecti=
on.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fhowdou-252Fedk2-=
252Fcommit-252F333c5f33adc652308355ec100f7f385d552392fa-26data-3D02-257C01-=
257Cbret.barkelew-2540microsoft.com-257Cffb03103e6ea44f2983d08d7d9d5f14d-25=
7C72f988bf86f141af91ab2d7cd011db47-257C1-257C0-257C637217385209311719-26sda=
ta-3DNARbUbs0zdooQRcLakblGydppgYFoxm1BBNhm4Ap4Ek-253D-26reserved-3D0%26d%3D=
DwMF-g%26c%3DC5b8zRQO1miGmBeVZ2LFWg%26r%3DJDRA6paRbJNUOHYumR0x1cbR-rntAJgCr=
G0B8Mn4tPQ%26m%3DPvJ44EXz_3NU_vi4-hYf3S1xX6CpQxua65zwio_7MPE%26s%3DpY_1X7py=
uTXznSH7ueWr_UcwaRD72_ezfbblCoh3vzQ%26e%3D&data=3D02%7C01%7Cbret.barkelew%4=
0microsoft.com%7Cdd228178329d45b6820708d7db66437f%7C72f988bf86f141af91ab2d7=
cd011db47%7C1%7C0%7C637219104584833006&sdata=3D2Jmqn4xh1CAA6TAxhFhq1lpseMai=
Dn%2BftzFuGIhtQlQ%3D&reserved=3D0>

I think it is not allowed to have FixAtBuild at IA32 and Dynamic at X64. B=
aseTool should have an error message for this.




--_000_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-=
1252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">AH! Okay. I would agree that a build crash without =
an actionable error is something we want to fix.</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">- Bret</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"mso-element:para-border-div;border:none;border-top:solid #E1=
E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class=3D"MsoNormal" style=3D"border:none;padding:0in"><b>From: </b><a h=
ref=3D"mailto:derek.lin2@hpe.com">Lin, Derek (HPS SW)</a><br>
<b>Sent: </b>Tuesday, April 7, 2020 7:40 PM<br>
<b>To: </b><a href=3D"mailto:devel@edk2.groups.io">devel@edk2.groups.io</a=
>; <a href=3D"mailto:Bret.Barkelew@microsoft.com">
Bret Barkelew</a><br>
<b>Subject: </b>RE: [edk2-devel] Basetools fail without error message due =
to PCD type differs in architecture.</p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Bret,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your feedb=
ack. I=92m very sorry that I didn=92t describe it clearly.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The Basetools just =
=93crash=94 in the configuration. The Basetools crash without any informat=
ion, then build stops.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I=92ve looked into th=
e BaseTools code, the python code crash, during the generation of PCD datab=
ase for IA32.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I=92m not sure if the=
 PCD spec allows different PCD type in different architectures.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If the spec allows it=
, the build needs to be fixed and make sure it works. I remember the dynami=
c PCD database carry from PEI to DXE. And I don=92t think that work if PEI =
is FixedAtBuild while DXE is Dyanamic.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In my opinion, this c=
onfiguration should come to a build failure. And define the error in PCD sp=
ec.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Derek<o:p></o:p></spa=
n></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></sp=
an></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in=
 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> devel@edk2.groups.io [mailto:devel@edk=
2.groups.io]
<b>On Behalf Of </b>Bret Barkelew via groups.io<br>
<b>Sent:</b> Wednesday, April 8, 2020 5:48 AM<br>
<b>To:</b> devel@edk2.groups.io; Lin, Derek (HPS SW) &lt;derek.lin2@hpe.co=
m&gt;<br>
<b>Subject:</b> Re: [EXTERNAL] [edk2-devel] Basetools fail without error m=
essage due to PCD type differs in architecture.<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This seems like a legitimate configuration. I don=
=92t know that it should be considered an error. A warning, maybe.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is also what the build report is perfect for f=
inding. Did you check the PCD build report when debugging?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">- Bret<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in=
 0in 0in">
<p class=3D"MsoNormal"><b>From: </b><a href=3D"mailto:derek.lin2=3Dhpe.com=
@groups.io">Lin, Derek (HPS SW) via groups.io</a><br>
<b>Sent: </b>Sunday, April 5, 2020 7:55 PM<br>
<b>To: </b><a href=3D"mailto:devel@edk2.groups.io">devel@edk2.groups.io</a=
><br>
<b>Subject: </b>[EXTERNAL] [edk2-devel] Basetools fail without error messa=
ge due to PCD type differs in architecture.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We've found a Basetool issue.&nbsp;<br>
When a PCD is FixAtBuild at IA32 and Dynamic is at X64, there is no error =
message in this situation and it's very difficult to find the root cause.<b=
r>
<br>
Here's example to see the issue:<br>
<a href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%=
2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__nam06.safelinks.p=
rotection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fhowdou-25=
2Fedk2-252Fcommit-252F333c5f33adc652308355ec100f7f385d552392fa-26data-3D02-=
257C01-257Cbret.barkelew-2540microsoft.com-257Cffb03103e6ea44f2983d08d7d9d5=
f14d-257C72f988bf86f141af91ab2d7cd011db47-257C1-257C0-257C63721738520931171=
9-26sdata-3DNARbUbs0zdooQRcLakblGydppgYFoxm1BBNhm4Ap4Ek-253D-26reserved-3D0=
%26d%3DDwMF-g%26c%3DC5b8zRQO1miGmBeVZ2LFWg%26r%3DJDRA6paRbJNUOHYumR0x1cbR-r=
ntAJgCrG0B8Mn4tPQ%26m%3DPvJ44EXz_3NU_vi4-hYf3S1xX6CpQxua65zwio_7MPE%26s%3Dp=
Y_1X7pyuTXznSH7ueWr_UcwaRD72_ezfbblCoh3vzQ%26e%3D&amp;data=3D02%7C01%7Cbret=
.barkelew%40microsoft.com%7Cdd228178329d45b6820708d7db66437f%7C72f988bf86f1=
41af91ab2d7cd011db47%7C1%7C0%7C637219104584833006&amp;sdata=3D2Jmqn4xh1CAA6=
TAxhFhq1lpseMaiDn%2BftzFuGIhtQlQ%3D&amp;reserved=3D0">https://github.com/ho=
wdou/edk2/commit/333c5f33adc652308355ec100f7f385d552392fa</a><br>
<br>
I think it is not allowed to have FixAtBuild at IA32 and Dynamic at X64. B=
aseTool should have an error message for this.
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_--

--_004_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_
Content-Type: image/png; name="ED2113367E40488891C9418E77E74F95.png"
Content-Description: ED2113367E40488891C9418E77E74F95.png
Content-Disposition: inline; filename="ED2113367E40488891C9418E77E74F95.png";
	size=156; creation-date="Wed, 08 Apr 2020 04:11:49 GMT";
	modification-date="Wed, 08 Apr 2020 04:11:49 GMT"
Content-ID: <image001.png@01D60D21.27BF2B10>
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAsQAAAADCAYAAACUJxmmAAAAAXNSR0IArs4c6QAAAARnQU1BAACx
jwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAxSURBVGhD7dYBDQAwDMOw8ic1BEdwMJ90GrWl
cEjm3CdJkiS19oc4AADQyhADANArWRCzbWwv0sXDAAAAAElFTkSuQmCC

--_004_CY4PR21MB0743989EE27B2EA630EE4187EFC00CY4PR21MB0743namp_--