From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.100; helo=mga07.intel.com; envelope-from=liming.gao@intel.com; receiver=edk2-devel@lists.01.org Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 7A6FD2202E497 for ; Wed, 14 Mar 2018 18:50:02 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Mar 2018 18:56:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,308,1517904000"; d="scan'208";a="24162728" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga007.fm.intel.com with ESMTP; 14 Mar 2018 18:56:25 -0700 Received: from fmsmsx153.amr.corp.intel.com (10.18.125.6) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 14 Mar 2018 18:56:25 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by FMSMSX153.amr.corp.intel.com (10.18.125.6) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 14 Mar 2018 18:56:24 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.226]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.235]) with mapi id 14.03.0319.002; Thu, 15 Mar 2018 09:56:23 +0800 From: "Gao, Liming" To: "Kinney, Michael D" , "edk2-devel@lists.01.org" Thread-Topic: [RFC] Remove X86 .asm and .S assembly files in EDK2 Thread-Index: AdOaeaGNXzeD3yDLSdiX/XGJTnXSdwgi5XNAAD6euCA= Date: Thu, 15 Mar 2018 01:56:22 +0000 Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1E6C13@SHSMSX104.ccr.corp.intel.com> References: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1B9F76@SHSMSX104.ccr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: [RFC] Remove X86 .asm and .S assembly files in EDK2 X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2018 01:50:02 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike: Now, %pragma macho subsections_via_symbols can't be enabled. So, will nas= m generate the bigger image size than .S assembly on macho? If yes, I agree= nasm is not same to .S. .S may be kept for a while. But, .asm is not neces= sary. We can remove .asm first.=20 Thanks Liming > -----Original Message----- > From: Kinney, Michael D > Sent: Wednesday, March 14, 2018 4:00 AM > To: Gao, Liming ; edk2-devel@lists.01.org; Kinney, = Michael D > Subject: RE: [RFC] Remove X86 .asm and .S assembly files in EDK2 >=20 > Liming, >=20 > After further evaluation on use of NASM with macho > there are a couple issues that need to be resolved > before the .asm and .S files can be removed from > all components. >=20 > The details are at: >=20 > https://bugzilla.tianocore.org/show_bug.cgi?id=3D881 >=20 > NASM issues to be resolved are: >=20 > https://bugzilla.nasm.us/show_bug.cgi?id=3D3392469 > https://bugzilla.nasm.us/show_bug.cgi?id=3D3392470 >=20 > The recommendation is to not switch to NASM only > for libraries until the dead code stripping feature > works as expected on macho. >=20 > We can consider moving to NASM only for NASM files > in a module if there are no NASM functions that would > be dead stripped. The recommendation for these types > of NASM files is do not use the following pragma > until the NASM issues above are resolved. >=20 > %pragma macho subsections_via_symbols >=20 > Best regards, >=20 > Mike >=20 > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel- > > bounces@lists.01.org] On Behalf Of Gao, Liming > > Sent: Wednesday, January 31, 2018 3:06 AM > > To: edk2-devel@lists.01.org > > Subject: [edk2] [RFC] Remove X86 .asm and .S assembly > > files in EDK2 > > > > Edk2 has used nasm assembly file for all tool chains. > > So, IA32 and X64 .asm and .S assembly files can be > > removed if their nasm files are ready. It can save the > > maintain effort and avoid the confuse. > > > > > > > > If you have any comments on this change, please let me > > know. > > > > Thanks > > Liming > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel