From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Disable o32 ABI for MIPS64 architectures
Date: Wed, 26 Mar 2014 18:18:35 +0100 [thread overview]
Message-ID: <53330BEB.3090206@mind.be> (raw)
In-Reply-To: <1395843340-18539-1-git-send-email-Vincent.Riera@imgtec.com>
On 26/03/14 15:15, Vicente Olivert Riera wrote:
> 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.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> CHANGES | 8 ++++++++
> arch/Config.in.mips | 12 +++++++-----
> 2 files changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/CHANGES b/CHANGES
> index 45a31c4..f07ccfd 100644
> --- a/CHANGES
> +++ b/CHANGES
> @@ -1,3 +1,11 @@
> +2014.05, Not yet released:
> +
> +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.
> +
> 2014.02, Released February 27th, 2014
>
> Minor fixes.
> diff --git a/arch/Config.in.mips b/arch/Config.in.mips
> index d9c0c02..f558705 100644
> --- a/arch/Config.in.mips
> +++ b/arch/Config.in.mips
> @@ -38,15 +38,12 @@ endchoice
>
> choice
> prompt "Target ABI"
> - depends on BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el
> - default BR2_MIPS_OABI32 if !BR2_ARCH_IS_64
> - default BR2_MIPS_NABI32 if BR2_ARCH_IS_64
> + depends on BR2_mips64 || BR2_mips64el
> + default BR2_MIPS_NABI32
>
> help
> Application Binary Interface to use
>
> -config BR2_MIPS_OABI32
> - bool "o32"
> config BR2_MIPS_NABI32
> bool "n32"
> depends on BR2_ARCH_IS_64
> @@ -86,6 +83,11 @@ config BR2_GCC_TARGET_ARCH
> default "mips64" if BR2_mips_64
> default "mips64r2" if BR2_mips_64r2
>
> +config BR2_MIPS_OABI32
> + bool
> + default y if BR2_mips || BR2_mipsel
> + default n if BR2_mips64 || BR2_mips64el
Did you forget to remove this or is there a reason to keep it? In the
latter case, please add an explanatory comment.
Regards,
Arnout
> +
> config BR2_GCC_TARGET_ABI
> default "32" if BR2_MIPS_OABI32
> default "n32" if BR2_MIPS_NABI32
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-03-26 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 14:15 [Buildroot] [PATCH v3] Disable o32 ABI for MIPS64 architectures Vicente Olivert Riera
2014-03-26 17:18 ` Arnout Vandecappelle [this message]
2014-03-26 18:03 ` Vicente Olivert Riera
2014-03-26 21:28 ` Peter Korsgaard
2014-03-27 9:56 ` Vicente Olivert Riera
2014-03-28 0:02 ` Joshua Kinard
2014-03-28 9:51 ` Vicente Olivert Riera
2014-03-28 10:27 ` Markos Chandras
2014-03-28 10:38 ` Vicente Olivert Riera
2014-03-28 10:41 ` Markos Chandras
2014-03-28 10:52 ` Joshua Kinard
2014-03-28 11:01 ` Vicente Olivert Riera
2014-03-28 11:07 ` Thomas Petazzoni
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=53330BEB.3090206@mind.be \
--to=arnout@mind.be \
--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