From: Elizabeth Oldham <beth@the-hug.org>
To: buildroot@busybox.net
Subject: [Buildroot] [MIPS] toolchain/gcc/Config.in broken
Date: Tue, 09 Oct 2007 20:42:35 +0100 [thread overview]
Message-ID: <470BD9AB.2020909@the-hug.org> (raw)
In-Reply-To: <20071009193325.GR20951@aon.at>
Bernhard Fischer wrote:
> On Tue, Oct 09, 2007 at 08:16:19PM +0100, Elizabeth Oldham wrote:
>
>
>>The matrix of MIPS ISA and ABIs supported on Linux is:
>>(fixed pitch font time)
>>
>> o32 n32 n64
>>MIPS I o
>>MIPS II o
>>MIPS III o o o
>>MIPS IV o o o
>>MIPS32(r1) o
>>MIPS32R2 o
>>MIPS64(r1) o o o
>>MIPS64R2 o o o
>>
>>(blank is not supported)
> And eabi looks much like n32 with a little adjustments here and there.
> I assume that o64 is supported on any n64 capable target, yes?
> Are there any endianess constraints or is this freely chooseable on all
> ISAs?
I'm not familar with eabi, I've not heard of it with reference to MIPS.
I'd have to ask my more learned colleagues :)
o64 is not supported on Linux, and not going to be AFAIK, but bare-iron
it would be as gcc can generate the code.
Once you have a supported ISA/ABI you can choose your endian with impunity.
Beth
next prev parent reply other threads:[~2007-10-09 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <470ADDA8.3080105@ruby.dti.ne.jp>
2007-10-09 7:08 ` [Buildroot] [MIPS] toolchain/gcc/Config.in broken Bernhard Fischer
2007-10-09 9:56 ` Shinya Kuribayashi
2007-10-09 12:27 ` Bernhard Fischer
2007-10-09 13:57 ` Shinya Kuribayashi
2007-10-09 16:30 ` Bernhard Fischer
2007-10-09 19:16 ` Elizabeth Oldham
2007-10-09 19:33 ` Bernhard Fischer
2007-10-09 19:42 ` Elizabeth Oldham [this message]
2007-10-09 20:56 ` Elizabeth Oldham
2007-10-09 21:31 ` Bernhard Fischer
2007-10-10 2:52 ` Shinya Kuribayashi
[not found] ` <120071009213155.GU20951@aon.at>
2007-10-10 10:13 ` Elizabeth Oldham
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=470BD9AB.2020909@the-hug.org \
--to=beth@the-hug.org \
--cc=buildroot@busybox.net \
/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