public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "rfc@edk2.groups.io" <rfc@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: Update NASM to stable release 2.15.05
Date: Thu, 21 Oct 2021 03:02:03 +0000	[thread overview]
Message-ID: <BN0PR11MB56960C5D2D532FFDDCBF29308CBF9@BN0PR11MB5696.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB4929DE0CEC0CB93EED5F0A4DD2BE9@CO1PR11MB4929.namprd11.prod.outlook.com>

Mike,
It‘s very good! It allows further NASM cleanup removing DB instructions.

Thanks,
Ray

-----Original Message-----
From: rfc@edk2.groups.io <rfc@edk2.groups.io> On Behalf Of Michael D Kinney
Sent: Thursday, October 21, 2021 12:52 AM
To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>; rfc@edk2.groups.io
Subject: [edk2-rfc] Update NASM to stable release 2.15.05

Hello,

I would like to propose that we update to a newer version of NASM.

	https://www.nasm.us/

The most recent stable version is 2.15.05.

	https://www.nasm.us/pub/nasm/releasebuilds/2.15.05/

NASM 2.15.05 Documentation:

	https://nasm.us/xdoc/2.15.05/html/
	https://nasm.us/xdoc/2.15.05/nasmdoc.pdf


The reason to update is to use a version of NASM that supports newer instructions that will allow the .nasm files with DB statements for instructions to be updated to use instruction names.  This improves the readability/maintenance of the .nasm source files:

	https://nasm.us/xdoc/2.15.05/html/nasmdocb.html#section-B.1.41

Also, the work on tools such as uncrustify to format source files require tests to make sure the source format changes do not cause any functional changes.  Compilers support flags for reproducible builds.  NASM 2.15.05 added the --reproducible flag that provides the same feature for OBJ files produces by NASM.

	https://nasm.us/xdoc/2.15.05/html/nasmdoc2.html#section-2.1.34


	2.1.34 The --reproducible Option
	
	If this option is given, NASM will not emit information that is
       inherently dependent on the NASM version or different from run to
       run (such as timestamps) into the output file.

Please let me know if there are any concerns with doing this tool update.
If there are no concerns, I will work on patches required to update EDK II CI to use NASM 2.15.05 and to update the developer documentation to require NASM 2.15.05 as the new minimum version.

Thanks,

Mike







      parent reply	other threads:[~2021-10-21  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 16:51 Update NASM to stable release 2.15.05 Michael D Kinney
2021-10-20 18:05 ` [edk2-devel] " Andrew Fish
2021-11-09 18:39   ` Michael D Kinney
2021-11-09 18:51     ` Andrew Fish
2021-10-21  3:02 ` Ni, Ray [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=BN0PR11MB56960C5D2D532FFDDCBF29308CBF9@BN0PR11MB5696.namprd11.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