[Top] [All Lists]

Re: RFC: Adding non-PIC executable support to MIPS

Subject: Re: RFC: Adding non-PIC executable support to MIPS
From: David VomLehn <>
Date: Mon, 30 Jun 2008 13:59:19 -0700
Authentication-results: sj-dkim-3;; dkim=pass ( sig from verified; );
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=1931; t=1214859569; x=1215723569; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;;; z=From:=20David=20VomLehn=20<> |Subject:=20Re=3A=20RFC=3A=20Adding=20non-PIC=20executable= 20support=20to=20MIPS |Sender:=20; bh=d46fpFyQnkLvWhMuSyP2GJn34oMmpFnBKSSB07c8amQ=; b=a/WTrXH6h8DTPEdZh0YIKnJ4Eh9KXJmDJOPfIL0UGSHWlbXDt4uIZSrGJ9 06F+o23Qm/XclKXdwKGrV9AMjLTClDTmA9qWJJ5cIQUhxMKCWWE6qYHbzg2O eO8oYW7BLN;
In-reply-to: <87y74pxwyl.fsf@firetop.home>
Original-recipient: rfc822;
References: <87y74pxwyl.fsf@firetop.home>
User-agent: Thunderbird (Windows/20080421)
Richard Sandiford wrote:
[Sorry for the 3-way crosspost!]

One of the big holes in the MIPS ABI has always been the lack of support
for non-PIC executables.

I'll describe my implementation
below, then compare it to what I understand CS's version to be.
CS folks: please correct me if I'm wrong.

This sounds like really good stuff and, on first reading, it all seems to make sense to me. My only real concern is documentation of these changes. The MIPS ABI ( is currently moribund. The document that describes it hasn't been updated in since 1996 and gcc is not fully conformant (see, for example, the assumptions required for correct stack backtracing). It would take significant work to resurrect this but it certainly would be helpful to have a current document that completely describes the MIPS ABI, or at least the current ELF format, as currently implemented on Linux, especially if it is to be extended. The logical home for something like this would probably be the Linux Standard Base project hosted by the Linux Foundation.

David VomLehn,
The opinions expressed herein are likely mine, but might not be my employer's...

- - - - - Cisco - - - - - This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.

<Prev in Thread] Current Thread [Next in Thread>