diff options
author | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2004-08-01 21:43:29 +0000 |
---|---|---|
committer | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2004-08-01 21:43:29 +0000 |
commit | 9f985f28b2e1bfdbbf871ab56280fffdb876eee6 (patch) | |
tree | 6cdee8944ce4a6a21b77e49df2f7c8f149bd4040 /doc | |
parent | 46a7303934d2a26623620e26771023efc4fbf208 (diff) | |
download | mdk-9f985f28b2e1bfdbbf871ab56280fffdb876eee6.tar.gz mdk-9f985f28b2e1bfdbbf871ab56280fffdb876eee6.tar.bz2 |
document mixasm -O option and delete references to -g.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/mdk_gstart.texi | 25 | ||||
-rw-r--r-- | doc/mdk_mixasm.texi | 17 | ||||
-rw-r--r-- | doc/mdk_mixvm.texi | 14 |
3 files changed, 27 insertions, 29 deletions
diff --git a/doc/mdk_gstart.texi b/doc/mdk_gstart.texi index 10302d4..9eab3f6 100644 --- a/doc/mdk_gstart.texi +++ b/doc/mdk_gstart.texi @@ -1,10 +1,10 @@ @c -*-texinfo-*- @c This is part of the GNU MDK Reference Manual. -@c Copyright (C) 2000, 2001, 2002, 2003 +@c Copyright (C) 2000, 2001, 2002, 2003, 2004 @c Free Software Foundation, Inc. @c See the file mdk.texi for copying conditions. -@c $Id: mdk_gstart.texi,v 1.16 2003/06/09 15:18:11 jao Exp $ +@c $Id: mdk_gstart.texi,v 1.17 2004/08/01 21:43:29 jao Exp $ @node Getting started, Emacs tools, MIX and MIXAL tutorial, Top @chapter Getting started @@ -116,17 +116,18 @@ the @file{hello.mixal} file, you can type the following command at your shell prompt: @example -mixasm -g hello @key{RET} +mixasm hello @key{RET} @end example @cindex .mix file If the source file contains no errors, this will produce a binary file called @file{hello.mix} which can be loaded and run by the MIX virtual -machine. The @code{-g} flag tells the assembler to include debug -information in the executable file (for a complete description of all -the compilation options, see @ref{mixasm}). Now, your are ready to run -your first MIX program, as described in the following section. +machine. Unless the @code{mixasm} option @code{-O} is provided, the +assembler will include debug information in the executable file (for a +complete description of all the compilation options, see +@ref{mixasm}). Now, your are ready to run your first MIX program, as +described in the following section. @node Running the program, Using mixguile, Compiling, Getting started @@ -459,11 +460,11 @@ MIX > @cindex @code{sbp} @cindex breakpoints @noindent -Note that, since we compiled @file{hello.mixal} with debug info enabled -(the @code{-g} flag of @code{mixasm}), the virtual machine is able to -tell us the line in the source file corresponding to the breakpoint we -are setting. As a matter of fact, you can directly set breakpoints at -source code lines using the command @code{sbp LINE_NO}, e.g. +Note that, since we compiled @file{hello.mixal} with debug info +enabled, the virtual machine is able to tell us the line in the +source file corresponding to the breakpoint we are setting. As a +matter of fact, you can directly set breakpoints at source code lines +using the command @code{sbp LINE_NO}, e.g. @example MIX > sbp 4 diff --git a/doc/mdk_mixasm.texi b/doc/mdk_mixasm.texi index c5d8765..4a956c1 100644 --- a/doc/mdk_mixasm.texi +++ b/doc/mdk_mixasm.texi @@ -1,10 +1,10 @@ @c -*-texinfo-*- @c This is part of the GNU MDK Reference Manual. -@c Copyright (C) 2000, 2001, 2003 +@c Copyright (C) 2000, 2001, 2003, 2004 @c Free Software Foundation, Inc. @c See the file mdk.texi for copying conditions. -@c $Id: mdk_mixasm.texi,v 1.7 2003/06/04 00:03:19 jao Exp $ +@c $Id: mdk_mixasm.texi,v 1.8 2004/08/01 21:43:29 jao Exp $ @node mixasm, mixvm, Emacs tools, Top @comment node-name, next, previous, up @@ -45,8 +45,8 @@ line options (note, that, following GNU's conventions, we provide a long option name for each available single letter switch): @example -mixasm [-vhulg] [-o OUTPUT_FILE] [--version] [--help] [--usage] - [--debug] [--output=OUTPUT_FILE] [--list[=LIST_FILE]] file +mixasm [-vhulO] [-o OUTPUT_FILE] [--version] [--help] [--usage] + [--ndebug] [--output=OUTPUT_FILE] [--list[=LIST_FILE]] file @end example @noindent @@ -64,10 +64,11 @@ Prints version and copyleft information and exits. Prints a summary of available options and exits. @end defopt -@defopt -g -@defoptx --debug -Includes debugging information in the compiled file, allowing breakpoint -setting at source level and symbol table inspection under @code{mixvm}. +@defopt -O +@defoptx --ndebug +Do not include debugging information in the compiled file, saving +space but disallowing breakpoint setting at source level and symbol +table inspection under @code{mixvm}. @end defopt @defopt -o output_file diff --git a/doc/mdk_mixvm.texi b/doc/mdk_mixvm.texi index 54655ab..ff7f567 100644 --- a/doc/mdk_mixvm.texi +++ b/doc/mdk_mixvm.texi @@ -4,7 +4,7 @@ @c Free Software Foundation, Inc. @c See the file mdk.texi for copying conditions. -@c $Id: mdk_mixvm.texi,v 1.17 2004/06/12 01:12:59 jao Exp $ +@c $Id: mdk_mixvm.texi,v 1.18 2004/08/01 21:43:29 jao Exp $ @node mixvm, gmixvm, mixasm, Top @comment node-name, next, previous, up @@ -290,9 +290,7 @@ MIX > @noindent since line 7 is the first one compiled into a MIX instruction (at -address 3000). In order to @code{sbp} to work, the source file must be -compiled using the @code{-g} flags, which tells @code{mixasm} to include -debug information in the binary @file{.mix} file. +address 3000). The command @code{cbp} clears a (previously set) breakpoint at the given source file line. @@ -367,9 +365,7 @@ START LDA VAR @noindent the symbol @code{VAR} stands for the value 2168, while @code{START} is -assigned the value 4000. When MIXAL programs are compiled using the -@code{-g} flag (which tells @code{mixasm} to include debug information -in the binary @file{.mix} file), the symbol table can be consulted from +assigned the value 4000. The symbol table can be consulted from the @code{mixvm} command line using @code{psym} followed by the name of the symbol whose contents you are interested in. When run without arguments, @code{psym} will print all defined symbols and their values. @@ -701,12 +697,12 @@ characters @code{%s} to mark the place where the source's file name will be inserted. For instance, if you type @example -MIX > sasm mixasm -g -l %s +MIX > sasm mixasm -l %s MIX > @end example issuing the @code{mixvm} command @w{@code{compile foo.mixal}} will invoke -the operating system command @w{@code{mixasm -g -l foo.mixal}}. +the operating system command @w{@code{mixasm -l foo.mixal}}. @code{pasm} prints the current value of the compile command template. |