From: Ralf Baechle <ralf@oss.sgi.com>
To: Lars Munch Christensen <c948114@student.dtu.dk>
Cc: linux-mips@oss.sgi.com
Subject: Re: mips64 linker bug?
Date: Sun, 22 Jul 2001 23:23:01 +0200 [thread overview]
Message-ID: <20010722232301.B13551@bacchus.dhis.org> (raw)
In-Reply-To: <20010722113923.A17752@tuxedo.skovlyporten.dk>; from c948114@student.dtu.dk on Sun, Jul 22, 2001 at 11:39:23AM +0200
On Sun, Jul 22, 2001 at 11:39:23AM +0200, Lars Munch Christensen wrote:
> I'm working on a very small, single address space, microkernel and I have
> the MIPS Malta with a 5Kc CPU to develop it on. The 5Kc is compatible
> with mips32 but I must admit, I really like to have my kernel
> running 64bit :). Is there a working binutils for 64 bit code floating
> around somewhere or should I stick with the mips32 stuff?
>
> I tried the binutil from ftp://ftp.ds2.pg.gda.pl/pub/macro/SRPMS/ but
> they where unable to compile with target mips64-linux.
Afaik the mips64-linux binutils are the only one that more (or more less ;)
work for building a 64-bit kernel. What we have to do to get around the
bugs and missing features is building a 64-bit kernel but passing -32 to
the assembler so we never use 64-bit ELF. In the end we convert the
resulting 32-bit ELF executable into 64-ELF using objcopy. That's about
as much as 64-bit binutils are usable for. For details see
arch/mips64/Makefile.
Ralf
prev parent reply other threads:[~2001-07-22 21:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-21 9:27 mips64 linker bug? Lars Munch Christensen
2001-07-21 15:23 ` Ralf Baechle
2001-07-21 16:17 ` Lars Munch Christensen
2001-07-21 19:07 ` Ralf Baechle
2001-07-22 9:39 ` Lars Munch Christensen
2001-07-22 10:35 ` Thiemo Seufer
2001-07-22 11:02 ` Kevin D. Kissell
2001-07-22 11:02 ` Kevin D. Kissell
2001-07-22 11:15 ` Thiemo Seufer
2001-07-22 11:44 ` Kevin D. Kissell
2001-07-22 11:44 ` Kevin D. Kissell
2001-07-22 21:23 ` Ralf Baechle [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=20010722232301.B13551@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=c948114@student.dtu.dk \
--cc=linux-mips@oss.sgi.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