Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ btou(1) — mips UMIPS RISC/os 5.01

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ucode(1)

utob(1)



BTOU(1)             RISC/os Reference Manual              BTOU(1)



NAME
     btou - MIPS Binary Ucode to ASCII Ucode converter

SYNOPSIS
     btou binary_file [ text_file ] [ -n ]

DESCRIPTION
     btou, the MIPS binary ucode to ASCII ucode converter, reads
     the binary ucode file and write it out in ASCII form in the
     file specified in the command line.  It checks the version
     stamp of the ucode file, and if it does not correspond to
     its own stamp, a warning message will be printed.  By con-
     vention, ASCII ucode files have the extension .U and binary
     ucode files have the extension .B, but btou does not force
     this convention on the user.  If the text file name is not
     given, the ASCII ucode is written to the standard output.
     btou will indent the ucode instructions to reflect their
     nesting levels within expressions, for easier readability.

     btou also reads the source file that generates the binary
     ucode and prints the source line next to each LOC instruc-
     tion as a COMM ucode. If the source file is not found, this
     operation is not performed.  Because of these additional
     COMM ucode instructions, the output ucode file actually con-
     tains more ucode instructions than the input ucode file.

     The following options are interpreted by btou.

     -n      Turns off indentation when printing the ucode
             instructions.  Any error detected in the ordering of
             the ucode instructions will not be detected.

SEE ALSO
     ucode(1), utob(1),

DIAGNOSTICS
     btou detects any error in the ordering of the ucode instruc-
     tions.  Such errors are detected while it recognizes the
     nesting levels of expressions, and it outputs the error mes-
     sages.  When such error occurs, the ucode instructions
     printed may not correspond to the original order in the
     input file.  In such a situation, the ucode instructions can
     be printed in their original order by using the -n flag.

NOTES
     If the input file is not a valid binary ucode file, btou can
     behave erratically and output garbage.








                        Printed 11/19/92                   Page 1



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026