Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: David VomLehn <dvomlehn@cisco.com>
Cc: 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 17:19:50 -0400	[thread overview]
Message-ID: <20080630211950.GA30847@caradoc.them.org> (raw)
In-Reply-To: <48694927.90906@cisco.com>

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...

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2008-06-30 21:20 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 [this message]
2008-06-30 21:28     ` David VomLehn
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=20080630211950.GA30847@caradoc.them.org \
    --to=dan@debian.org \
    --cc=binutils@sourceware.org \
    --cc=dvomlehn@cisco.com \
    --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