-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/15/2014 07:00 AM, Anthony G. Basile wrote:
> Hi everyone,
>
> I'm writing the arm team because of bug #515130 #c11. What would we
> like the MULTILIB_ABIS use flags to be for arm and arm64? 32-bit arm
> has two abis, the old abi sometimes called 'oabi' and the new one called
> 'eabi' --- e for embedded. oabi is pretty much dead, but the name eabi
> sticks around. Eg CHOST tuples for arm often end in -gnueabi or
> -uclibceabi.
>
> Sooo ...
>
> So we want the abi_arm_32 and abi_arm_64 for the two arches or do we
> want abi_arm_eabi and abi_arm_64? Or what? It is elegant to have
> abi_arm_{32,64} but it isn't what the common 32-bit abi is called. I
> don't even know what the "common" 64-bit is since 64-bit is so far
> uncommon.
Although I am one of the leads, this is above my skill level. I gladly
yield to the higher skill level of people like steev, vapier or tgall on
this.
Thanks,
Zero
>
> If you let me know, I'll implement the changes in the tree.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTxaQiAAoJEKXdFCfdEflKPyEP/iNoX6SnoBEjELjles2JJi7f
h6sysTcwuUFr0VzfWt3Ga0vM9OmciDQDGk4aEZq5uNub41sMvey4kEme6+l9ESiy
2I89L4A0tPyvAZO8gdu2pC/g3WZBYIED/BhC/cn/72wDaTOLRDa8I1YMKIR7DJbx
iCBa96R153RCr3ux2IAm9sdOY5IvuvQxy4Pv5YZPuzRRJnGl1CX9HooXlkuicr1J
+ugsxpW0PhZxv8JmsVLl7WMu9O/4cff8aWjEOXOypRizzN3n3rxYe2JZZe9VBTRa
EtB2OuazopkZTMY/y078+Dpi8oPodwjJaj3cOR1ECHdOGdNEGvm2+hSSPYfd6Oxz
kiaQ5taSe7B1OEPHVZH1HyIeCYXUKL2Zx/UwXIe67hFG0AZrLfmrDdgi/gv1tvVm
Jl2jKnRPNsmdUsddIfGECABu54DYwbk+15ywUDYlzxQuZwrGwIyBA2/4HY0bBY4o
Mu9GP0IFV7DYyXZ7xzlYeXJ/gAXTg9gaYiFm7X47LMSul7hBEqpgn4A0IRSuhHmV
plCGIRi4W9DhMyy5J2aNgjIByEYwJ3NHWJTY1Gvuz3ZOBXCAfFq2OYJ6E8xXHlDJ
/SUXGfvHcSdUxuUQ7M9gZUnUEQrng8VUMZBB4ISiRqEAcRqObdM5UjvA9H/LOjYH
7XDvhm1AzqPNtoHbreHC
=SoAY
-----END PGP SIGNATURE-----
Hash: SHA1
On 07/15/2014 07:00 AM, Anthony G. Basile wrote:
> Hi everyone,
>
> I'm writing the arm team because of bug #515130 #c11. What would we
> like the MULTILIB_ABIS use flags to be for arm and arm64? 32-bit arm
> has two abis, the old abi sometimes called 'oabi' and the new one called
> 'eabi' --- e for embedded. oabi is pretty much dead, but the name eabi
> sticks around. Eg CHOST tuples for arm often end in -gnueabi or
> -uclibceabi.
>
> Sooo ...
>
> So we want the abi_arm_32 and abi_arm_64 for the two arches or do we
> want abi_arm_eabi and abi_arm_64? Or what? It is elegant to have
> abi_arm_{32,64} but it isn't what the common 32-bit abi is called. I
> don't even know what the "common" 64-bit is since 64-bit is so far
> uncommon.
Although I am one of the leads, this is above my skill level. I gladly
yield to the higher skill level of people like steev, vapier or tgall on
this.
Thanks,
Zero
>
> If you let me know, I'll implement the changes in the tree.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTxaQiAAoJEKXdFCfdEflKPyEP/iNoX6SnoBEjELjles2JJi7f
h6sysTcwuUFr0VzfWt3Ga0vM9OmciDQDGk4aEZq5uNub41sMvey4kEme6+l9ESiy
2I89L4A0tPyvAZO8gdu2pC/g3WZBYIED/BhC/cn/72wDaTOLRDa8I1YMKIR7DJbx
iCBa96R153RCr3ux2IAm9sdOY5IvuvQxy4Pv5YZPuzRRJnGl1CX9HooXlkuicr1J
+ugsxpW0PhZxv8JmsVLl7WMu9O/4cff8aWjEOXOypRizzN3n3rxYe2JZZe9VBTRa
EtB2OuazopkZTMY/y078+Dpi8oPodwjJaj3cOR1ECHdOGdNEGvm2+hSSPYfd6Oxz
kiaQ5taSe7B1OEPHVZH1HyIeCYXUKL2Zx/UwXIe67hFG0AZrLfmrDdgi/gv1tvVm
Jl2jKnRPNsmdUsddIfGECABu54DYwbk+15ywUDYlzxQuZwrGwIyBA2/4HY0bBY4o
Mu9GP0IFV7DYyXZ7xzlYeXJ/gAXTg9gaYiFm7X47LMSul7hBEqpgn4A0IRSuhHmV
plCGIRi4W9DhMyy5J2aNgjIByEYwJ3NHWJTY1Gvuz3ZOBXCAfFq2OYJ6E8xXHlDJ
/SUXGfvHcSdUxuUQ7M9gZUnUEQrng8VUMZBB4ISiRqEAcRqObdM5UjvA9H/LOjYH
7XDvhm1AzqPNtoHbreHC
=SoAY
-----END PGP SIGNATURE-----