From: Khem Raj <kraj@mvista.com>
To: binutils@sourceware.org
Subject: Problem with 2.16 MIPS as (MIPS TLS support)
Date: Wed, 27 Apr 2005 23:43:00 -0000 [thread overview]
Message-ID: <427005A6.90604@mvista.com> (raw)
In-Reply-To: <426FFBE1.9010608@tlen.pl>
Hi,
The following instruction usage
lw $3,%tpoff(foo)($28)
is giving error on mips 2.16 as
while going through
http://www.linux-mips.org/wiki/index.php/NPTL
It mentions this intructions use in initial exec TLS model
but 2.16 gas seems not to understand tpoff relocation directive
Has 'tpoff' directive been implemented with a different name in 2.16
Thanks
-Khem
next prev parent reply other threads:[~2005-04-27 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 21:37 problem with ar Bambero
2005-04-27 23:43 ` Khem Raj [this message]
2005-04-28 1:08 ` Problem with 2.16 MIPS as (MIPS TLS support) Daniel Jacobowitz
2005-05-05 10:12 ` problem with ar Nick Clifton
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=427005A6.90604@mvista.com \
--to=kraj@mvista.com \
--cc=binutils@sourceware.org \
/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).