From: David VomLehn <dvomlehn@cisco.com>
To: David VomLehn <dvomlehn@cisco.com>,
binutils@sourceware.org, gcc@gcc.gnu.org,
linux-mips@linux-mips.org, rdsandiford@googlemail.com
Subject: Re: RFC: Adding non-PIC executable support to MIPS
Date: Mon, 30 Jun 2008 14:28:50 -0700 [thread overview]
Message-ID: <48695012.4080306@cisco.com> (raw)
In-Reply-To: <20080630211950.GA30847@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Mon, Jun 30, 2008 at 01:59:19PM -0700, David VomLehn wrote:
>> 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.
>
> FWIW, I'll be posting our version of this project shortly, and it
> includes an ABI supplement. Supplemental to a somewhat hypothetical
> document, but there you go...
Also, FWIW, if there is interest in trying to get an Linux Standard Base working
group for the MIPS Processor, one of the LSB Steering Committee members used to
be Chair of the MIPS ABI Group Technical Committee, which wrote the MIPS ABI.
And, uh, yeah, I'll admit it, I used to chair the TC, too, once upon a time. So,
we actually still have some people around who at least used to know something
about it...
--
David VomLehn, dvomlehn@cisco.com
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.
next prev parent reply other threads:[~2008-06-30 21:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 17:58 RFC: Adding non-PIC executable support to MIPS Richard Sandiford
2008-06-30 20:59 ` David VomLehn
2008-06-30 21:19 ` Daniel Jacobowitz
2008-06-30 21:28 ` David VomLehn [this message]
2008-07-01 20:22 ` Daniel Jacobowitz
2008-07-01 20:43 ` Richard Sandiford
2008-07-01 22:02 ` Richard Sandiford
2008-07-02 7:00 ` Adam Nemet
2008-07-02 10:13 ` Thiemo Seufer
2008-07-02 12:08 ` Daniel Jacobowitz
2008-07-02 19:55 ` Richard Sandiford
2008-07-02 20:29 ` Daniel Jacobowitz
2008-07-24 16:16 ` Daniel Jacobowitz
2008-07-24 20:17 ` Daniel Jacobowitz
2008-07-24 20:24 ` Richard Sandiford
2008-07-24 20:56 ` Daniel Jacobowitz
2008-07-27 9:10 ` Richard Sandiford
2008-07-27 21:36 ` Mark Mitchell
2008-07-28 19:43 ` Richard Sandiford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48695012.4080306@cisco.com \
--to=dvomlehn@cisco.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-mips@linux-mips.org \
--cc=rdsandiford@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox