From: Daniel Jacobowitz <dan@debian.org>
To: weasel@cs.stanford.edu
Cc: Eric Christopher <echristo@redhat.com>,
binutils@sources.redhat.com, linux-mips@oss.sgi.com
Subject: Re: me vs gas mips64 relocation
Date: Sun, 3 Feb 2002 02:26:51 -0500 [thread overview]
Message-ID: <20020203022651.A1903@nevyn.them.org> (raw)
In-Reply-To: <m24rkz5fz1.fsf@meer.net>
On Sat, Feb 02, 2002 at 08:47:30PM -0800, d p chang wrote:
> Eric Christopher <echristo@redhat.com> writes:
>
> > > ideas? (other than for me to take the crack pipe out of my ass)
> >
> > You can try to help Thiemo Seufer finish n32 and n64 support in
> > binutils...
>
> Is there a todo or something that I could start w/?
Search for TODO in elf64-mips.c, if I recall correctly. Among other
things PIC support is non-functional.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-02-03 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 13:45 me vs gas mips64 relocation d p chang
2002-02-01 20:52 ` d p chang
2002-02-01 21:23 ` Eric Christopher
2002-02-03 4:47 ` d p chang
2002-02-03 7:26 ` Daniel Jacobowitz [this message]
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=20020203022651.A1903@nevyn.them.org \
--to=dan@debian.org \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=linux-mips@oss.sgi.com \
--cc=weasel@cs.stanford.edu \
/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