Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!tk From: tk@clyde.UUCP Newsgroups: comp.lang.lisp,comp.unix.wizards,comp.unix.questions,att.unix Subject: help with COFF, KCL incremental loader Message-ID: <10900@clyde.ATT.COM> Date: Thu, 9-Jul-87 14:06:35 EDT Article-I.D.: clyde.10900 Posted: Thu Jul 9 14:06:35 1987 Date-Received: Sat, 11-Jul-87 14:06:40 EDT Sender: nuucp@clyde.ATT.COM Reply-To: tk@clyde.ATT.COM (Tom Kirk) Organization: AT&T Bell Laboratories, Whippany NJ Lines: 29 Keywords: pc-relative relocation types Xref: utgpu comp.lang.lisp:288 comp.unix.wizards:2923 comp.unix.questions:2795 junk:5427 I'm in need of assistance in understanding COFF files, in particular relocation information, on Vaxen. I currently have an incremental loader that works under SVR3 on a 3B2/400, and I'm attempting to make this work on an 8600. The loader is relatively simple; the important difference seems to be the way address relocation is handled. The thing I'm stumbling on is that I don't really understand how the "PC relative" relocation types work on the Vax. I've tried to gain some knowledge by looking at the code for the link editor, and have found trying to understand that code nearly intractable. Is there anyone that could: 1) explain pc-relative relocation types with respect to vaxes, and how they are treated, or 2) point me to where I can find this information (the COFF manual gives no details in this regard). By the way, this incremental loader is the one supplied with the Kyoto Common Lisp distribution. If someone has already done the work that I'm trying to do, that would solve my problem too. I was able to get KCL built for our Vaxen running SVR2 with little difficulty, only the loader needs to be ported to have a complete system. Any help that I can find would be much appreciated. Thanks. -------- tom kirk moss!tk at&t bell laboratories (201) 386-6044