Re: [Mingw-w64-public] [PATCH] mingw-w64-crt: Build system changes for ARM

[André H. <ne...@da...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 27.05.2014 01:04, schrieb JonY:
> On 5/27/2014 05:23, André Hentschel wrote:
>>> I don't see any obvious problems with it. Just one question though, does
>>> the ARM compiler also interpret -m32/-m64?
>>
>>> If so, there should be some checks added to prevent accidentally trying
>>> to build x86 stuff with it. Of course, the check can come in later.
>>
>> Thx for the review, i pushed it after fixing some obvious bugs.
>> The ARM gcc bails out on -m32/-m64... Do you mean a check like the existing one for libce?
>>
> 
> That too, I'm just wondering what will the ARM compiler do with
> -m32/-m64 or if multilib is even possible given that ARM has recently
> introduced 64bit CPUs.

- -m32/-m64 even alerts with aarch64 aware compilers, the architectures are strictly separated.
On aarch32 there are switches like -marm and -mthumb(2), but i really doubt that we should wait for -m32/-m64 on ARM. At the moment we also should focus on aarch32 and don't even care about aarch64 until we have a working toolchain.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQGcBAEBAgAGBQJThhurAAoJEGm5GZTakYssAJUL/jrhSTAdOSOqDlyQQbqAxlxl
zAcIMc5JqLJqvPfbCUSGMrJ6uH8gYHggLtk5KBAalym08vFnErAwwk5b6JQC+9Eu
Xb5fj199CwdeVX/fMR2nkjyS6UruVvYoLHtEqXW+e7z21K9KHMNR1Sd1hxJaaMhk
aN19rHLAOv10WBXayAHxFBhW8THy4Lyu9i2OlDVyAFDRX03Hu5htPj7ut9ST1J5D
EmIp7oHKsE8UK+g6w2KX6RDxJGa0yIlagoHv6zIxABWxHe8eNEb9ztP7bROQ4JrG
BAUDf368Qh5Ha8U5B4QBmmRKTxXeBwtLkZ/RV+7nh6y0mVKUqRoApPhLVIHLUzlY
IeejaW6/d/u6A7icSzPsMHHT+44Q5fkFq6xd5IiDLaOy1KgEPNI3cauE0OcfjeIJ
jXG2AIBTBh/wIHHBKKumbse/Zyr+Fj6tMqEDJTsKcZfRFW1vQZmeKHE54oTPI1/V
ZIqWdlDU28AXN3KcHFdoMmr58fOYSUhAG0uQlku3qQ==
=Vq0K
-----END PGP SIGNATURE-----