public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Richard Sandiford <rsandifo@redhat.com>, binutils@sources.redhat.com
Subject: Re: TLS support for MIPS
Date: Wed, 09 Feb 2005 00:21:00 -0000	[thread overview]
Message-ID: <1107894139.5047.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20050208160059.GA9847@nevyn.them.org>


> > We already have separate operators for things like R_MIPS_CALL_HI16 and
> > R_MIPS_CALL_LO16, namely %call_hi() and %call_lo()[*].  I think it'd be
> > simpler and more consistent to have %dtpoff_hi() and %dtpoff_lo()
> > instead.  You'd then be able to get rid of hackery like:
> 
> I cribbed this approach from PowerPC (@tprel@ha) because it seemed
> eminently sensible.  If you'd prefer to use single operators instead,
> then I guess I can crib from a different architecture instead.
> 

It is fairly sensible, however, it doesn't really fit like we've been
going. Cribbing from alpha would probably work.


> OK.  At this point I think that means renaming the relocations; I just
> renamed the operators more sanely recently.  Anyone have a preference
> on the TPREL vs. TPOFF conventions?
> 

I prefer rel, but that's possibly just my bias.

-eric

  reply	other threads:[~2005-02-08 20:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  9:30 Daniel Jacobowitz
2005-02-08 13:42 ` Alan Modra
2005-02-21 19:23   ` Daniel Jacobowitz
2005-02-22  9:23     ` Alan Modra
2005-02-08 16:26 ` Richard Sandiford
2005-02-08 18:04   ` Daniel Jacobowitz
2005-02-09  0:21     ` Eric Christopher [this message]
2005-02-09  7:07     ` Thiemo Seufer
2005-02-09  8:17 ` Thiemo Seufer
2005-02-24 21:56 ` Daniel Jacobowitz
2005-03-02  2:07   ` Thiemo Seufer
2005-03-03 10:27   ` Richard Sandiford
2005-03-03 14:28     ` Daniel Jacobowitz
2005-03-03 15:03       ` 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=1107894139.5047.23.camel@localhost.localdomain \
    --to=echristo@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=drow@false.org \
    --cc=rsandifo@redhat.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).