From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <03c967468426e68ecebb05a11f0077ff@terzarima.net> From: Charles Forsyth Date: Tue, 6 Jan 2009 20:11:34 +0000 To: lucio@proxima.alt.za, 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-sskraqdbqndsqnicvqiufguxat" Subject: Re: [9fans] Format for relocatable objects Topicbox-Message-UUID: 7acafe52-ead4-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-sskraqdbqndsqnicvqiufguxat Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit .[8kvq965] ... files are unrelated to a.out. as ken thompson's paper says The object files are binary forms of assembly language, similar to what might be passed between the first and second passes of an assembler. they contain target-dependent code but not precise machine instructions (the loader makes the final choice of machine instructions). one nice thing about the scheme is that in the compiler suite only the loader knows or needs to know the bit patterns and peculiar properties of the actual machine. --upas-sskraqdbqndsqnicvqiufguxat Content-Type: message/rfc822 Content-Disposition: inline Received: from gouda.swtch.com ([67.207.142.3]) by lavoro; Tue Jan 6 19:02:53 GMT 2009 Received: from localhost ([127.0.0.1] helo=gouda.swtch.com) by gouda.swtch.com with esmtp (Exim 4.67) (envelope-from <9fans-bounces@9fans.net>) id 1LKGxQ-0004qa-Qc; Tue, 06 Jan 2009 18:47:16 +0000 Received: from tracker.proxima.alt.za ([192.96.32.140] helo=mutter.proxima.alt.za) by gouda.swtch.com with esmtp (Exim 4.67) (envelope-from ) id 1LKGxN-0004qV-PG for 9fans@9fans.net; Tue, 06 Jan 2009 18:47:14 +0000 Received: from plan9.phyrql.alt.za (oblm-ip-nas-1-p47.telkom-ipnet.co.za [155.239.76.47]) (authenticated bits=0) by mutter.proxima.alt.za (8.14.3/8.14.3) with ESMTP id n06IAM2F024096 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <9fans@9fans.net>; Tue, 6 Jan 2009 20:10:24 +0200 (SAST) Message-ID: To: 9fans@9fans.net Organization: Proxima Research & Development Date: Tue, 6 Jan 2009 20:47:06 +0200 From: lucio@proxima.alt.za MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: [9fans] Format for relocatable objects X-BeenThere: 9fans@9fans.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces@9fans.net Errors-To: 9fans-bounces+forsyth=terzarima.net@9fans.net Where should I look for the format of Plan 9 objects as created by the compiler(s) and ready for linking? I'm hoping there is a place other than the compiler sources that documents this intermediate format, which I presume is not totally unlike a.out. Also, while I'm asking, there must be more than a hint of ELF in the Linux emulation code, can someone point me to the details? ELF is low on my list of favourites, but there may be some useful shortcuts in giving it a bit of recognition under Plan 9. ++L PS: in case the context isn't obvious, GNU CC and C++ for Plan 9 are the eventual objectives, I'm taking a slightly circular approach in an attempt to understand David Hogan's work a lot better than I do now. --upas-sskraqdbqndsqnicvqiufguxat--