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: Fri, 10 Dec 2004 09:34:00 -0000 [thread overview]
Message-ID: <wvny8g61oqe.fsf@talisman.cambridge.redhat.com> (raw)
In-Reply-To: <m3llc78lqd.fsf@gossamer.airs.com> (Ian Lance Taylor's message of "09 Dec 2004 11:44:42 -0500")
Ian Lance Taylor <ian@wasabisystems.com> writes:
>> 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?
>
> For n32 the patch is to gcc, not the binutils. I have that patch, but
> it's a new feature and as such is not going to be acceptable in stage
> 3. I'll submit it when gcc goes back to stage 1.
OK. I was just wondering if there was a specific reason for making
.cpload (the o32 pseudo-op) use _gp but not .cpsetup (the n32 pseudo-op).
I realise that most n32 code uses %hi/lo(%neg(%gp_rel(...))) directly,
but some hand-written asm does use .cpsetup.
> The gcc patch looks more or like the following, plus some obvious
> mips.h and doc stuff.
Looks good, but would it be possible to use SYMBOL_GENERAL instead of
adding a new symbol type like SYMBOL_GP? In hindsight, "SYMBOL_ABSOLUTE"
would probably have been a better name than SYMBOL_GENERAL.
Richard
next prev parent reply other threads:[~2004-12-10 9:34 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
2004-12-09 16:44 ` Ian Lance Taylor
2004-12-10 9:34 ` Richard Sandiford [this message]
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=wvny8g61oqe.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).