From: Joshua Kinard <kumba@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Disable o32 ABI for MIPS64 architectures
Date: Wed, 26 Mar 2014 19:34:33 -0400 [thread overview]
Message-ID: <53336409.8090402@gentoo.org> (raw)
In-Reply-To: <5332E203.9040904@imgtec.com>
On 03/26/2014 10:19, Markos Chandras wrote:
> On 03/26/2014 12:14 AM, Joshua Kinard wrote:
>> On 03/25/2014 16:02, Arnout Vandecappelle wrote:
>>> On 25/03/14 18:52, Vicente Olivert Riera wrote:
[snip]
>>> Support for MIPS o32 ABI on MIPS-64 targets has been removed. Building
>>> o32 ELF files for MIPS64 is an exotic configuration that nobody should be
>>> using. If o32 is required, then is better if it's built for MIPS 32-bit
>>> cores so only 32-bit instructions will be used leading to a more
>>> efficient o32 usage.
>>
>> Just to point out, I wouldn't call this "exotic" -- o32 on mips64 kernels
>> (MIPS-IV ISA) is what I run on my SGI O2 under Gentoo. That said, I do have
>> a somewhat-working n32 chroot on the same box. Additionally, isn't o32 the
>> ABI that Debian still builds for most of their mips/mipsel targets?
>
> We are talking about using 64-bit instructions in *userland* while
> maintaining the o32 ABI semantics. Well, this is definitely an exotic
> configuration. We are not talking about 64-bit kernels + o32 userland.
> An o32 userland usually comes from mips32 and you usually have only 32-bit
> instructions there.
I think the mixup I am having is the "MIPS64" that Vincent is referring to
is the ISA, e.g., mips64r[12], not "MIPS64" as in "64bit MIPS", right?
--
Joshua Kinard
Gentoo/MIPS
kumba at gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
prev parent reply other threads:[~2014-03-26 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 17:52 [Buildroot] [PATCH v2] Disable o32 ABI for MIPS64 architectures Vicente Olivert Riera
2014-03-25 20:02 ` Arnout Vandecappelle
2014-03-26 0:14 ` Joshua Kinard
2014-03-26 14:19 ` Markos Chandras
2014-03-26 14:24 ` Vicente Olivert Riera
2014-03-26 17:17 ` Arnout Vandecappelle
2014-03-26 23:45 ` Joshua Kinard
2014-03-27 9:27 ` Markos Chandras
2014-03-26 23:34 ` Joshua Kinard [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=53336409.8090402@gentoo.org \
--to=kumba@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.