Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84 chuqui version 1.9 3/12/85; site unisoft.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!umcp-cs!gymble!lll-crg!dual!unisoft!fnf
From: fnf@unisoft.UUCP
Newsgroups: net.lang.c
Subject: dis(1) on S5R2
Message-ID: <496@unisoft.UUCP>
Date: Tue, 9-Jul-85 18:47:55 EDT
Article-I.D.: unisoft.496
Posted: Tue Jul  9 18:47:55 1985
Date-Received: Fri, 12-Jul-85 00:46:04 EDT
References: <474@crystal.UUCP> <420@enmasse.UUCP> <2367@sun.uucp> <422@gatech.CSNET> <463@sftri.UUCP> <2391@sun.uucp>
Reply-To: fnf@unisoft.UUCP
Distribution: net
Organization: UniSoft Systems, Berkeley
Lines: 21

In article <2391@sun.uucp> guy@sun.uucp (Guy Harris) writes:
>> AT&T compilers these days all come with a tool, call "dis", for
>> disassembler. that look at object files and tell you exactly what
>> instructions are in them.
>
>Well, some AT&T compilers, anyway - the S5R2 documentation describes DIS(1)
>as "3B20 only".

Dis(1) is a standard part of our S5R2 unix port (UniPlus).  It is
from the generic 68000 microport done by Motorola Microsystems.
Thus most system V ports based on the generic 68000 port should contain
the new SGS (Software Generation System) based C compiler and the
disassembler.  By the way, the output of dis is *NOT* suitable as
input to the assembler (sigh).

-Fred

===========================================================================
Fred Fish    UniSoft Systems Inc, 739 Allston Way, Berkeley, CA  94710  USA
{ucbvax,decvax}!unisoft!fnf	(415) 644 1230 		TWX 11 910 366-2145
===========================================================================