diff options
| author | Debbie Wiles <debs@dwiles.demon.co.uk> | 2002-05-17 15:54:24 +0000 |
|---|---|---|
| committer | Debbie Wiles <debs@dwiles.demon.co.uk> | 2002-05-17 15:54:24 +0000 |
| commit | 93c50efe347e086771aad526d491aa96e0d8d964 (patch) | |
| tree | 386d4b9160a916b9fa15aa672099eae0704582fc /doc | |
| parent | 873e68c1cd14dfce46868acaa6e8a43139e28a13 (diff) | |
| download | nasm-93c50efe347e086771aad526d491aa96e0d8d964.tar.gz nasm-93c50efe347e086771aad526d491aa96e0d8d964.tar.bz2 nasm-93c50efe347e086771aad526d491aa96e0d8d964.zip | |
Changed address to report bugs in ndisasm appendix.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/nasmdoc.src | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src index 544f2ec..6f086dc 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -3198,7 +3198,7 @@ When NASM is in \c{BITS 16} state, instructions which use 32-bit data are prefixed with an 0x66 byte, and those referring to 32-bit addresses have an 0x67 prefix. In \c{BITS 32} state, the reverse is true: 32-bit instructions require no prefixes, whereas instructions -using 16-bit data need an 0x66 and those working in 16-bit addresses +using 16-bit data need an 0x66 and those working on 16-bit addresses need an 0x67. The \c{BITS} directive has an exactly equivalent primitive form, @@ -6220,7 +6220,8 @@ anyway. There are no known bugs. However, any you find, with patches if possible, should be sent to \W{mailto:jules@dsf.org.uk}\c{jules@dsf.org.uk} or \W{mailto:anakin@pobox.com}\c{anakin@pobox.com}, or to the -developer's site \W{http://nasm.2y.net/}\c{http://nasm.2y.net/} +developer's site at +\W{https://sourceforge.net/projects/nasm/}\c{https://sourceforge.net/projects/nasm/} and we'll try to fix them. Feel free to send contributions and new features as well. |