Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!ksand From: ksand@Apple.COM (Kent Sandvik) Newsgroups: comp.unix.aux Subject: Re: MacApp->C++->A/UX Message-ID: <51781@apple.Apple.COM> Date: 21 Apr 91 19:31:01 GMT References: <3151@skivs.UUCP> <51729@apple.Apple.COM> Organization: Apple Computer Inc., Cupertino, CA Lines: 33 In article urlichs@smurf.sub.org (Matthias Urlichs) writes: >In comp.unix.aux, article <51729@apple.Apple.COM>, > ksand@Apple.COM (Kent Sandvik) writes: >< Hmm, a better question would be "Are there any plans to support COFF >< format from the MPW environment?" >It's possible to convert COFF to MPW. >The main problem is that due to the nonrelocatability of COFF code, if you >want to link COFF stuff you have to put everything in data space (i.e. >A5-relative). This includes the executable code. Yes, a good example of binaries compiled under cc and moved to the MacOS environment are the tools under standalone shell. If you ever wondered why your System/Finder won't start sash, well maybe an init or something else that increases your system heap has taken over memory space above about 639k (0x9FC00), and the modules require data addresses starting from that point. So changing globals to use A5-relative offsets is a must. >Is there any good way to feed object code back into the assembler? Dumpobj >isn't very good at producing reasemblable output. Maybe an additional option >for dumpobj is in order here; it would certainly simplify things. >Apple? I have to talk with the DSG people - the idea is good. Maybe there's a way, but I'm not aware of it. Kent Sandvik -- Disclaimer: Private and personal activities on USENET, non-company sponsored