This is the mail archive of the
mailing list for the binutils project.
Re: [PATCH] Fix distinction of 32/64bit addresses in MIPS gas
- To: binutils at sources dot redhat dot com
- Subject: Re: [PATCH] Fix distinction of 32/64bit addresses in MIPS gas
- From: Thiemo Seufer <ica2_ts at csv dot ica dot uni-stuttgart dot de>
- Date: Thu, 6 Sep 2001 20:14:49 +0200
- References: <20010831193107.A10362@rembrandt.csv.ica.uni-stuttgart.de> <firstname.lastname@example.org> <email@example.com> <20010831204556.C17249@rembrandt.csv.ica.uni-stuttgart.de> <firstname.lastname@example.org> <email@example.com> <20010831143107.A4532@lucon.org> <firstname.lastname@example.org> <20010906105014.A32456@lucon.org> <email@example.com>
> "mips64-elf" tools have, historically, generated:
> * 32-bit ELF
> * mips3-compatible code (including use of full 64-bit GPRs).
> Unless you say -mlong64, pointers and longs will be 32-bit, but you'll
> use full 64-bit GPRs for 'long long'.
> If you do say -mlong64, you'll get 64-bit pointers and longs, in your
> 64-bit GPRs.
> All with a 32-bit ELF format. (And, using R_MIPS_64 to represent
> pointers in the object files.)
> I don't really _know_ what ABI it uses. I had always thought of it as
> "o64", which in my mind was "o32 naively extended for 64-bit GPRs,"
> but really i don't know that that's correct.
Does this mean o64 doesn't allow 64bit addressing?
Btw, is there _any_ description/pamphlet/whatever about what o64 is?
> In fact, I don't really
> _care_ what ABI it uses. We understand the calling conventions well
> enough for embedded development use, which is where we're using it.
What calling convention does it use?