Xref: utzoo comp.sys.intel:573 comp.sys.misc:1913
Path: utzoo!attcan!uunet!pcrat!rick
From: rick@pcrat.UUCP (Rick Richardson)
Newsgroups: comp.sys.intel,comp.sys.misc
Subject: Re: Good C and Lint for RMX86
Keywords: C, RMX
Message-ID: <609@pcrat.UUCP>
Date: 5 Nov 88 12:19:00 GMT
References: <3371@pt.cs.cmu.edu> <7144@dasys1.UUCP> <4708@cadnetix.COM> <7258@dasys1.UUCP> <14386@dhw68k.cts.com>
Reply-To: rick@pcrat.UUCP (Rick Richardson)
Organization: PC Research, Inc., Tinton Falls, NJ
Lines: 25

In article <14386@dhw68k.cts.com> doug@dhw68k.cts.com (Doug Salot) writes:
>I believe that SSI (Costa Mesa, CA 714/241-8650) and Pharlap (I dunno
>where) have tools that will allow you to use Microsoft object generating
>compilers/assemblers for OMF environments.  I haven't had the chance
>to use either of the products extensively, so I can't make any claim
>as to their usefulness.

I used the Pharlap stuff to convert MSC to OMF back in June '88.  At that
time it was strictly global variables and functions as far as symbols
go.  No types, lines numbers, or locals.  I gave the person at Pharlap
a sample of the output of a COFF to OMF converter I wrote which did
handle line numbers and some types, so it is quite likely that they
have improved the functionality for MSC .OBJ's.

Pharlap was very responsive, as I recall.  They had some trouble
initially with ICE86, which is why I sent samples of COFF converted
to OMF.  The older ICE's make assumptions about OMF that aren't
necessarily true unless you use Intel language products.  I had
already beat my head on this one in making the COFF converter.

-- 
Rick Richardson | JetRoff "di"-troff to LaserJet Postprocessor|uunet!pcrat!dry2
PC Research,Inc.| Mail: uunet!pcrat!jetroff; For anon uucp do:|for Dhrystone 2
uunet!pcrat!rick| uucp jetroff!~jetuucp/file_list ~nuucp/.    |submission forms.
jetroff Wk2200-0300,Sa,Su ACU {2400,PEP19200} 12013898963 "" \r ogin: jetuucp