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

2008-07-28 Thread Richard Sandiford
Mark Mitchell <[EMAIL PROTECTED]> writes: > Richard Sandiford wrote: >> Daniel Jacobowitz <[EMAIL PROTECTED]> writes: >>> All comments welcome - Richard, especially from you. How would you >>> like to proceed? I think the first step should be to get your other >>> binutils/gcc patches merged, inc

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

2008-07-27 Thread Mark Mitchell
Richard Sandiford wrote: Daniel Jacobowitz <[EMAIL PROTECTED]> writes: All comments welcome - Richard, especially from you. How would you like to proceed? I think the first step should be to get your other binutils/gcc patches merged, including MIPS16 PIC; I used those as a base. But see a fe

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

2008-07-27 Thread Richard Sandiford
Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > All comments welcome - Richard, especially from you. How would you > like to proceed? I think the first step should be to get your other > binutils/gcc patches merged, including MIPS16 PIC; I used those as a > base. But see a few of the notes for p

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

2008-07-24 Thread Daniel Jacobowitz
On Thu, Jul 24, 2008 at 09:24:48PM +0100, Richard Sandiford wrote: > > - I've dropped support for a non-fixed $gp. This is a handy > > optimization, but it was getting in the way and it was the part of the > > GCC patch Richard had the most comments on. I can resubmit it after > > everything else

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

2008-07-24 Thread Richard Sandiford
Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > - Richard's ld -r support is an addition to the ABI, but does not > conflict with anything else, so I included it. I discovered two > potential problems: > > - If a symbol with STO_MIPS_PIC is localized using objcopy, > binutils will ignore the f

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

2008-07-24 Thread Daniel Jacobowitz
On Thu, Jul 24, 2008 at 12:16:20PM -0400, Daniel Jacobowitz wrote: > I have attached Let's all pretend I attached this glibc patch, instead of the one in my previous message, please. -- Daniel Jacobowitz CodeSourcery 2008-07-24 Mark Shinwell <[EMAIL PROTECTED]> Daniel Jacobowitz <[EMAIL

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

2008-07-02 Thread Daniel Jacobowitz
On Wed, Jul 02, 2008 at 08:55:54PM +0100, Richard Sandiford wrote: > The size of the header and first 0x1 stubs would be the same. > I think it would also preserve the resolver interface while removing > the need for the extra-large .plts. The only incompatibility I can > see would be that obj

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

2008-07-02 Thread Richard Sandiford
Thanks to everyone for their kind messages. I won't drag this out for non-MIPS folk by replying publicly to each one. Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > the GOT cleanups in particular look very useful. Thanks. To be clear: the withdrawal was simply for the patches in this message.

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

2008-07-02 Thread Daniel Jacobowitz
On Tue, Jul 01, 2008 at 09:43:30PM +0100, Richard Sandiford wrote: > I suppose I still support the trade-off between the 5-insn MIPS I stubs > (with extra-long variation for large PLT indices) and the absolute > .got.plt address I used. And I still think it's shame we're treating > STO_MIPS_PLT an

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

2008-07-02 Thread Thiemo Seufer
Richard Sandiford wrote: > Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > > We've shipped our version. Richard's version has presumably also > > shipped. > > Right. > > > We did negotiate the ABI changes with MTI; this is not quite > > as good as doing it in full view, but it was the best we co

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

2008-07-02 Thread Adam Nemet
Richard Sandiford writes: > However, IMO, your argument about MTI being the central authority > is a killer one. The purpose of the GNU tools should be to follow > appropriate standards where applicable (and extend them where it > seems wise). So from that point of view, I agree that the GNU tool

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

2008-07-01 Thread Richard Sandiford
Richard Sandiford <[EMAIL PROTECTED]> writes: > I've been thinking about that a lot recently, since I heard about > your implementation. I kind-of guessed it had been agreed with MTI > beforehand (although I hadn't realised MTI themselves had written > the specification). Having thought it over,

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

2008-07-01 Thread Richard Sandiford
Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > We've shipped our version. Richard's version has presumably also > shipped. Right. > We did negotiate the ABI changes with MTI; this is not quite > as good as doing it in full view, but it was the best we could manage > and MTI is as close to a cen

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

2008-06-30 Thread Daniel Jacobowitz
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