Opened 3 years ago
Closed 3 years ago
#19595 closed enhancement (fixed)
nasm-2.16.02
| Reported by: | Bruce Dubbs | Owned by: | thomas |
|---|---|---|---|
| Priority: | normal | Milestone: | 12.2 |
| Component: | BOOK | Version: | git |
| Severity: | medium | Keywords: | |
| Cc: |
Description
New point version.
Change History (3)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.

configureor dependency generation.configurethink it was running native when in fact cross-compiling.PATH_MAXlimit to any pathname; this is unnecessary.PTWRITEopcode corrected (F3prefix required.)NP; notably the prefixed versions ofCLACareERETU/ERETS.LKGS,ERETSandERETUinstructions.obj(OMF) and possibly other output formats.%map()function to expand a macro from a list of arguments, see "f_map".=modifier in "define".__USE_package__is now__?USE_package?__.D*x* statements, see "db".%repblocks.%num(), see "f_num".%hex()function, equivalent to%eval()except that it producess hexadecimal values that are nevertheless valid NASM numeric constants, see "f_hex".%*num* references to multi-line macro arguments.)binformat is simply a linker built into NASM. See "binfmt".LOCKprefix warning forXCHG.LOCK XCHGreg,mem would issue a warning for being unlockable, which is incorrect. In this case the reg,mem encoding is simply an alias for the mem,reg encoding. However,XCHGis always locked, so create a new warning(
-w+prefix-lock-xchg) to explicitly flag a user-specifiedLOCK XCHG; default off. Future versions of NASM may remove theLOCKprefix when optimization is enabled.-w+reloc-*, see "warnings"), default off.Dx statements, such asdb 1 2. See "db".