From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] external-toolchain: Allow MIPS64 for Codesourcery MIPS toolchains
Date: Sun, 26 May 2013 15:29:10 +0200 [thread overview]
Message-ID: <20130526152910.2a32ecbb@skate> (raw)
In-Reply-To: <1368627740-4094-1-git-send-email-markos.chandras@gmail.com>
Dear Markos Chandras,
On Wed, 15 May 2013 15:22:20 +0100, Markos Chandras wrote:
> From: Markos Chandras <markos.chandras@imgtec.com>
>
> The n64 ABI which is supported by the Codesourcery MIPS toolchains,
> is only available with MIPS64 so allow these cores to be selected
> and used with these toolchains.
>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
> ---
> toolchain/toolchain-external/Config.in | 20 ++++++++++----------
> 1 files changed, 10 insertions(+), 10 deletions(-)
I've just tested this one, and with the following defconfig:
BR2_mips64el=y
BR2_MIPS_NABI64=y
BR2_TOOLCHAIN_EXTERNAL=y
the Busybox compilation fails with:
In file included from libbb/pw_encrypt.c:89:0:
libbb/pw_encrypt_des.c: In function 'pw_encrypt':
libbb/pw_encrypt_des.c:289:27: internal compiler error: in gen_rtx_SUBREG, at emit-rtl.c:769
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://support.codesourcery.com/GNUToolchain/> for instructions.
make[2]: *** [libbb/pw_encrypt.o] Erreur 1
It does not appear with the same toolchain in MIPS32 mode. I agree it's
a toolchain bug, but I'm just wondering in which conditions you tested
your patch and/or if something can be done to avoid the toolchain
breakage.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-26 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 14:22 [Buildroot] [PATCH] external-toolchain: Allow MIPS64 for Codesourcery MIPS toolchains Markos Chandras
2013-05-26 13:29 ` Thomas Petazzoni [this message]
2013-05-27 9:05 ` Markos Chandras
2013-05-27 9:18 ` Thomas Petazzoni
2013-05-27 15:11 ` Markos Chandras
2013-06-07 8:53 ` Markos Chandras
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=20130526152910.2a32ecbb@skate \
--to=thomas.petazzoni@free-electrons.com \
--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