summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@zytor.com>2017-02-23 17:19:56 -0800
committerH. Peter Anvin <hpa@zytor.com>2017-02-23 17:19:56 -0800
commitf805cdebe20bffe97c5df9c058a6f1852a6f80eb (patch)
tree943ac8b257905a024a6be1f913df7239a067d50f
parent1a3314f64b687279d436ad1a07b907a7243c8274 (diff)
downloadnasm-f805cdebe20bffe97c5df9c058a6f1852a6f80eb.tar.gz
changes.src: update to fit current 2.13 branch status
It is kind of sad and impressive at the same time how little of the 2.13 changes are actually user-visible at this point. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
-rw-r--r--doc/changes.src20
1 files changed, 18 insertions, 2 deletions
diff --git a/doc/changes.src b/doc/changes.src
index 04ded0f5..a7944fe0 100644
--- a/doc/changes.src
+++ b/doc/changes.src
@@ -7,6 +7,22 @@
The NASM 2 series supports x86-64, and is the production version of NASM
since 2007.
+\S{cl-2.13} Version 2.13
+
+\b Support the official forms of the \c{UD0} and \c{UD1} instructions.
+
+\b Allow self-segment-relative expressions in immediates and
+ displacements, even when combined with an external or otherwise
+ out-of-segment special symbol, e.g.:
+
+\c extern foo
+\c mov eax,[foo - $ + ebx] ; Now legal
+
+\b Handle a 64-bit origin in NDISASM.
+
+\b NASM can now generate sparse output files for relevant output
+ formats, if the underlying operating system supports them.
+
\S{cl-2.12.03} Version 2.12.03
\b Add new warnings for certain dangerous constructs which never ought
@@ -1328,7 +1344,7 @@ it 0.98.28 to not confuse poor little apt-get.
Changes from 0.98.07 release to 98.09b as of 28-Oct-2001
\b More closely compatible with 0.98 when -O0 is implied
-or specified. Not strictly identical, since backward
+or specified. Not strictly identical, since backward
branches in range of short offsets are recognized, and signed
byte values with no explicit size specification will be
assembled as a single byte.
@@ -2045,7 +2061,7 @@ on lines such as `dd 0.0,0.0,0.0,0.0,...'
\b Fixed a subtle preprocessor bug whereby invoking one multi-line
macro on the first line of the expansion of another, when the second
had been invoked with a label defined before it, didn't expand the
-inner macro.
+inner macro.
\b Added internal.doc back in to the distribution archives - it was
missing in 0.96 *blush*