| To: | Eric Christopher <echristo@redhat.com> |
|---|---|
| Subject: | Re: recent binutils and mips64-linux |
| From: | "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> |
| Date: | Fri, 19 Sep 2003 14:52:35 +0200 (MET DST) |
| Cc: | Atsushi Nemoto <nemoto@toshiba-tops.co.jp>, Daniel Jacobowitz <dan@debian.org>, linux-mips@linux-mips.org, binutils@sources.redhat.com |
| In-reply-to: | <1063949984.2537.0.camel@ghostwheel.sfbay.redhat.com> |
| Organization: | Technical University of Gdansk |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
On Thu, 18 Sep 2003, Eric Christopher wrote: > > But mips64 kernel assumes that the kernel itself is compiled with > > "-mabi=64". For example, some asm routines pass more than 4 arguments > > via aN registers. > > Yes, but then you aren't abi compliant are you? If you want n64 then say > n64. If you want o32 extended to 64-bit registers then use o64. I think "-mabi=64" is OK (I use it for over a year now) and for those worried of every byte of precious memory, "-mabi=n32 -mlong64" might be the right long-term answer (although it might require verifying if tools handle it right). Given the experimental state of the 64-bit kernel it should be OK to be less forgiving on a requirement for recent tools. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available + |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: mips64 cpu-probe.c compile failure, Maciej W. Rozycki |
|---|---|
| Next by Date: | list archive, Dominik 'Rathann' Mierzejewski |
| Previous by Thread: | Re: recent binutils and mips64-linux, Eric Christopher |
| Next by Thread: | Re: recent binutils and mips64-linux, Eric Christopher |
| Indexes: | [Date] [Thread] [Top] [All Lists] |