| To: | Atsushi Nemoto <nemoto@toshiba-tops.co.jp> |
|---|---|
| Subject: | Re: recent binutils and mips64-linux |
| From: | Eric Christopher <echristo@redhat.com> |
| Date: | Thu, 18 Sep 2003 22:39:45 -0700 |
| Cc: | Daniel Jacobowitz <dan@debian.org>, linux-mips@linux-mips.org, binutils@sources.redhat.com |
| In-reply-to: | <20030919.122940.45519247.nemoto@toshiba-tops.co.jp> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20030918212727.GA24686@nevyn.them.org> <1063940280.2423.13.camel@ghostwheel.sfbay.redhat.com> <20030919.122940.45519247.nemoto@toshiba-tops.co.jp> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Thu, 2003-09-18 at 20:29, Atsushi Nemoto wrote: > >>>>> On Thu, 18 Sep 2003 19:58:00 -0700, Eric Christopher > >>>>> <echristo@redhat.com> said: > echristo> mips-linux-gcc -mabi=32 -march=64bitarch is my suggestion. > > 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. -eric -- Eric Christopher <echristo@redhat.com> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: recent binutils and mips64-linux, Daniel Jacobowitz |
|---|---|
| Next by Date: | Re: recent binutils and mips64-linux, Atsushi Nemoto |
| Previous by Thread: | Re: recent binutils and mips64-linux, Atsushi Nemoto |
| Next by Thread: | Re: recent binutils and mips64-linux, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |