summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorCyrill Gorcunov <gorcunov@gmail.com>2009-12-22 23:36:46 +0300
committerCyrill Gorcunov <gorcunov@gmail.com>2009-12-22 23:42:07 +0300
commit3e73cfc8b77c39a61f3a393aa4e65d1da83d6d4d (patch)
tree96d6317b7aed80d8cafd939361fd6f371c1c6622 /doc
parentfaaad6e75d82f3228298b01a61b08eb37ca10bb4 (diff)
downloadnasm-3e73cfc8b77c39a61f3a393aa4e65d1da83d6d4d.tar.gz
nasm-3e73cfc8b77c39a61f3a393aa4e65d1da83d6d4d.tar.bz2
nasm-3e73cfc8b77c39a61f3a393aa4e65d1da83d6d4d.zip
doc/nasmdoc.src: Update the number of sync points in docs
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/nasmdoc.src2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 77a2cae..b98c3be 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -7813,7 +7813,7 @@ ideal.
To avoid this, you can specify a `\i\c{synchronisation}' point, or indeed
as many synchronisation points as you like (although NDISASM can
-only handle 8192 sync points internally). The definition of a sync
+only handle 2147483647 sync points internally). The definition of a sync
point is this: NDISASM guarantees to hit sync points exactly during
disassembly. If it is thinking about generating an instruction which
would cause it to jump over a sync point, it will discard that