external-toolchain: Allow MIPS64 for Codesourcery MIPS toolchains

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(-)

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

On 26 May 2013 14:29, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> 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

Hi Thomas,

I did limited testing and I haven't seen this problem but I haven't
build busybox to be honest.
However, on the release notes they say they support MIPS64/n64
https://sourcery.mentor.com/GNUToolchain/release2358?@template=datasheet

so I just allowed buildroot to select this combination as well.

My understanding is that the compilation problem is orthogonal to
mip64/n64 patch in the sense
that forbidding the combination just hides the problem for now :)

--
Regards,
Markos Chandras

Dear Markos Chandras,

On Mon, 27 May 2013 10:05:10 +0100, Markos Chandras wrote:

> I did limited testing and I haven't seen this problem but I haven't
> build busybox to be honest.
> However, on the release notes they say they support MIPS64/n64
> https://sourcery.mentor.com/GNUToolchain/release2358?@template=datasheet
> 
> so I just allowed buildroot to select this combination as well.
> 
> My understanding is that the compilation problem is orthogonal to
> mip64/n64 patch in the sense
> that forbidding the combination just hides the problem for now :)

I agree that the problem is orthogonal, but having an external
toolchain that isn't even capable of building Busybox worries me a
little bit. This means that an user selecting mips64 and external
toolchain, and keep all the other options as default, will see a
failing build. Not really nice.

We have various issues with the toolchain from Mentor Graphics. It
would be nice if we could have some contact to help solve those issues.

Best regards,

Thomas

On 27 May 2013 10:18, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Dear Markos Chandras,
>
> On Mon, 27 May 2013 10:05:10 +0100, Markos Chandras wrote:
>
>> I did limited testing and I haven't seen this problem but I haven't
>> build busybox to be honest.
>> However, on the release notes they say they support MIPS64/n64
>> https://sourcery.mentor.com/GNUToolchain/release2358?@template=datasheet
>>
>> so I just allowed buildroot to select this combination as well.
>>
>> My understanding is that the compilation problem is orthogonal to
>> mip64/n64 patch in the sense
>> that forbidding the combination just hides the problem for now :)
>
> I agree that the problem is orthogonal, but having an external
> toolchain that isn't even capable of building Busybox worries me a
> little bit. This means that an user selecting mips64 and external
> toolchain, and keep all the other options as default, will see a
> failing build. Not really nice.

Ok I agree. I will try an out-of-buildroot build for busybox using
this toolchain just to rule out specific buildroot problems. If that
fails too then I will see if there is a way to report this problem.

--
Regards,
Markos Chandras

On 27 May 2013 16:11, Markos Chandras <markos.chandras@gmail.com> wrote:
> On 27 May 2013 10:18, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Dear Markos Chandras,
>>
>> On Mon, 27 May 2013 10:05:10 +0100, Markos Chandras wrote:
>>
>>> I did limited testing and I haven't seen this problem but I haven't
>>> build busybox to be honest.
>>> However, on the release notes they say they support MIPS64/n64
>>> https://sourcery.mentor.com/GNUToolchain/release2358?@template=datasheet
>>>
>>> so I just allowed buildroot to select this combination as well.
>>>
>>> My understanding is that the compilation problem is orthogonal to
>>> mip64/n64 patch in the sense
>>> that forbidding the combination just hides the problem for now :)
>>
>> I agree that the problem is orthogonal, but having an external
>> toolchain that isn't even capable of building Busybox worries me a
>> little bit. This means that an user selecting mips64 and external
>> toolchain, and keep all the other options as default, will see a
>> failing build. Not really nice.
>
> Ok I agree. I will try an out-of-buildroot build for busybox using
> this toolchain just to rule out specific buildroot problems. If that
> fails too then I will see if there is a way to report this problem.
>
> --
> Regards,
> Markos Chandras

Thomas,

busybox now builds on the 2013.05 toolchain. I will send a patch for
the version bump and add MIPS64 support as well.

--
Regards,
Markos Chandras