Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site utcsri.UUCP
Path: utzoo!utcsri!tarvydas
From: tarvydas@utcsri.UUCP (Paul Tarvydas)
Newsgroups: net.micro.atari16
Subject: Re: .o file format description wanted
Message-ID: <3120@utcsri.UUCP>
Date: Thu, 17-Jul-86 21:58:59 EDT
Article-I.D.: utcsri.3120
Posted: Thu Jul 17 21:58:59 1986
Date-Received: Thu, 17-Jul-86 22:24:57 EDT
References: <3856@utah-cs.UUCP>
Reply-To: tarvydas@utcsri.UUCP (Paul Tarvydas)
Organization: CSRI, University of Toronto
Lines: 20
Summary: 

It turns out that the .o format IS documented - DRI CP/M 68K manual,
section 3 "Command File Format".  It's similar to Unix in that the
executable format is the same as the object format, except that
the symbols have been resolved and possibly stripped out.  "Relmod"
does some further processing, but this is after everything has been linked,
and I haven't bothered to finger out what it's effect is.

You can easily identify the sections of a .o file described in the
manual by using "dump.prg" on some (small) .o file.  As far as I can
tell, the symbol types "defined", "equated" and "equated register"
are possibly white elephants - they're probably used as flags by
the assembler, then the whole symbol table is just dumped out to
the .o file; but, I haven't investigated that thoroughly yet, so
don't stake your life on it.

Send me mail if you want to discuss it further - I'm still exploring.

Paul Tarvydas
Tarvydas-Sanford Controls Inc.
...{ihnp4|...}!utcsri!tarvydas