[Top] [All Lists]

RE: [PATCH, RFC] MIPS: Implement the getcontext API

To: "Joseph Myers" <>, "Ralf Baechle" <>
Subject: RE: [PATCH, RFC] MIPS: Implement the getcontext API
From: "David VomLehn (dvomlehn)" <>
Date: Thu, 5 Mar 2009 17:08:18 -0500
Authentication-results: rtp-dkim-1;; dkim=pass ( sig from verified; );
Cc: "David Daney" <>, "Maciej W. Rozycki" <>, <>, <>, "Maciej W. Rozycki" <>, "Richard Sandiford" <>
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=1880; t=1236290899; x=1237154899; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;;; z=From:=20=22David=20VomLehn=20(dvomlehn)=22=20<dvomlehn@cis> |Subject:=20RE=3A=20[PATCH,=20RFC]=20MIPS=3A=20Implement=20 the=20getcontext=20API |Sender:=20 |To:=20=22Joseph=20Myers=22=20<>,=0A =20=20=20=20=20=20=20=20=22Ralf=20Baechle=22=20<ralf@linux-m>; bh=vKwgj+ZUuHHGblUz09Hyc+6ZekVPHss3LRmLtMGe4dk=; b=nenzj3N3T8pwglFHjCQ0D0MwHthZoPL0rjljCO+bzmqZGmHvyPv3606oeh AqDkKsRHzwWuVLlotkJgZWa70bb6PddsvRjFydV+2tu6hU4PJ93d4MDsDrt+ 5osxkm5Iq1;
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <> <> <> <> <>
Thread-index: Acmd3Nkuz4Q900bBQfa7KqWkCfRlNAAAWe2w
Thread-topic: [PATCH, RFC] MIPS: Implement the getcontext API
> -----Original Message-----
> From: Joseph Myers [] 
> Sent: Thursday, March 05, 2009 1:53 PM
> To: Ralf Baechle
> Cc: David VomLehn (dvomlehn); David Daney; Maciej W. Rozycki; 
>;; Maciej 
> W. Rozycki; Richard Sandiford
> Subject: Re: [PATCH, RFC] MIPS: Implement the getcontext API
> On Thu, 5 Mar 2009, Ralf Baechle wrote:
> > stillborn EABI and NUBI variants.  Add various Linux and 
> GNU specific
> > enhancements and deviations from the previously mentioned 
> documents for
> > example for TLS.  Frequently the documentation really is 
> just in the code,
> > a mailing list archive or in the back of somebody's brain ...
> (Although it took a while for the documentation to catch up with the 
> implementation and changes made in the course of patch 
> review, as far as I 
> know <> is now an accurate 
> description 
> of TLS for MIPS.)
> > Somebody could probably earn a medal by writing a single 
> consolidated
> > and readable piece of documentation.
> Anyone seriously wishing to produce a complete and current and 
> copyright-clean description of what the MIPS ABIs now are 
> might wish to 
> note that a similar project for (32-bit) Power Architecture 
> has been going 
> on since late 2006 and we still haven't quite got to the point of 
> releasing a public review draft.  There is a lot of work involved.

I spent two years as Chair of the MIPS ABI Group Technical Committee
working on the MIPS psABI and I can attest to how much work it is.
Still, if there were enough of people involved from the kernel,
compiler/library, and appropriate utility communities willing to try to
pull things together, I could see spending time on it.

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