From: Daniel Jacobowitz <dan@debian.org>
To: 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: Thu, 24 Jul 2008 16:56:48 -0400 [thread overview]
Message-ID: <20080724205647.GA18897@caradoc.them.org> (raw)
In-Reply-To: <87ej5j2fov.fsf@firetop.home>
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 is merged.
>
> That's a shame. It was also the bit I liked best ;) What went wrong?
>
> (My comments were only minor.)
Nothing big: but it made up the bulk of our GCC patch, and I was
rebasing on top of yours. We had a lot of trouble getting that bit to
work, so I took the conservative path and dropped it. Don't worry - I
definitely will return to this as soon as the remaining patches are
merged; I liked it too.
Originally, we were also going to make small data work with non-PIC
abicalls. I'd like to discuss that with you at some later date too.
We ran into a lot of trouble combining small data with a non-fixed
$gp; I believe it was because reload may introduce small data loads
very late. I'd have to try it again before I had anything more
sensible to say, though.
> Sorry for the bugs, and thanks for fixing them. I'll try to have
> a look at the patches over the weekend.
No problem, and thank you for looking at them - and for your patches;
I'm really pretty happy with the combined work.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-24 20:56 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
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 [this message]
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=20080724205647.GA18897@caradoc.them.org \
--to=dan@debian.org \
--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