From: Richard Sandiford <rsandifo@redhat.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: binutils@sourceware.org
Subject: Re: News MIPS option -mno-shared
Date: Thu, 09 Dec 2004 16:41:00 -0000 [thread overview]
Message-ID: <wvnacsn1l2o.fsf@talisman.cambridge.redhat.com> (raw)
In-Reply-To: <20041209153403.5294.qmail@gossamer.airs.com> (Ian Lance Taylor's message of "9 Dec 2004 10:34:03 -0500")
Ian Lance Taylor <ian@wasabisystems.com> writes:
> This patch adds a new option to the MIPS assembler: -mno-shared.
> Normally the .cpload pseudo-op generates code which looks like this:
>
> lui $gp,%hi(_gp_disp)
> addiu $gp,$gp,%lo(_gp_disp)
> addu $gp,$gp,.cpload argument
>
> With -mno-shared, the .cpload pseudo-op will generate code that looks
> like this:
>
> lui $gp,%hi(_gp)
> addiu $gp,$gp,%lo(_gp)
>
> The idea is that you can use -KPIC -mno-shared and get code which
> still uses the usual Unix calling convention, but is slightly more
> efficient at each function entry.
Yeah, this has been on my to-do list for a while ;) Are you going to
do the same thing for n32 or are you only interested in o32?
FWIW, the patch looks good to me if it's o32 only.
Richard
next prev parent reply other threads:[~2004-12-09 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 15:34 Ian Lance Taylor
2004-12-09 16:41 ` Richard Sandiford [this message]
2004-12-09 16:44 ` Ian Lance Taylor
2004-12-10 9:34 ` Richard Sandiford
2004-12-11 3:45 ` Ian Lance Taylor
2004-12-09 16:53 ` Thiemo Seufer
2004-12-09 18:03 ` David Daney
2004-12-09 20:32 ` Ian Lance Taylor
2004-12-10 13:45 ` Dave Korn
2004-12-10 14:12 ` Thiemo Seufer
2004-12-09 18:19 ` Maciej W. Rozycki
2004-12-09 21:05 ` Ian Lance Taylor
2004-12-09 18:52 ` David Daney
2004-12-09 21:20 ` Ian Lance Taylor
2005-02-21 22:42 ` David Daney
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=wvnacsn1l2o.fsf@talisman.cambridge.redhat.com \
--to=rsandifo@redhat.com \
--cc=binutils@sourceware.org \
--cc=ian@wasabisystems.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).