1 |
On 12/29/2013 09:52 PM, Anthony G. Basile wrote: |
2 |
> On 12/29/2013 04:48 PM, Markos Chandras wrote: |
3 |
>> On 12/29/2013 09:48 PM, Michał Górny wrote: |
4 |
>>> Dnia 2013-12-29, o godz. 16:40:08 |
5 |
>>> Joshua Kinard <kumba@g.o> napisał(a): |
6 |
>>> |
7 |
>>>> On 12/28/2013 5:58 PM, Michał Górny wrote: |
8 |
>>>>> I've noticed today that mips uses the same CHOST value for all three |
9 |
>>>>> ABIs it supports: |
10 |
>>>>> |
11 |
>>>>> arch/mips/mips64/multilib/make.defaults:CHOST_o32="${CHOST}" |
12 |
>>>>> arch/mips/mips64/multilib/make.defaults:CHOST_n32=${CHOST} |
13 |
>>>>> arch/mips/mips64/multilib/make.defaults:CHOST_n64=${CHOST} |
14 |
>>>>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_o32="${CHOST}" |
15 |
>>>>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n32="${CHOST}" |
16 |
>>>>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n64="${CHOST}" |
17 |
>>>>> |
18 |
>>>>> [...] |
19 |
>>>> |
20 |
>>>> Matt can probably vouch for this better, but the only two ABIs |
21 |
>>>> affected by |
22 |
>>>> this are n32 and n64. mips[el]-unknown-linux-gnu implies a 32-bit |
23 |
>>>> big/little endian CHOST, which means the o32 ABI. |
24 |
>>>> mips64[el]-unknown-linux-gnu means either n32 or n64. So no change |
25 |
>>>> should |
26 |
>>>> be needed for o32-based installs. |
27 |
>>> |
28 |
>>> Just to be clear: |
29 |
>>> |
30 |
>>> profiles/arch/mips/mipsel/mips64el/multilib/make.defaults: |
31 |
>>> |
32 |
>>> CHOST="mips64el-unknown-linux-gnu" |
33 |
>>> |
34 |
>>> [...] |
35 |
>>> |
36 |
>>> CFLAGS_o32="-mabi=32" |
37 |
>>> CHOST_o32="${CHOST}" |
38 |
>>> |
39 |
>>> CFLAGS_n32="-mabi=n32" |
40 |
>>> CHOST_n32="${CHOST}" |
41 |
>>> |
42 |
>>> CFLAGS_n64="-mabi=64" |
43 |
>>> CHOST_n64="${CHOST}" |
44 |
>>> |
45 |
>>> So in this case, o32 actually uses mips64el-unknown-linux-gnu, unless |
46 |
>>> I'm missing something. |
47 |
>>> |
48 |
>> |
49 |
>> Yes all 3 ABIs use the same tuple. |
50 |
>> |
51 |
> |
52 |
> I think people are missing Mike's point from earlier, which is that |
53 |
> tuples label toolchains and a toolchain can support multiple abis. So |
54 |
> for example, what would one do on a system which simultaneously has o32, |
55 |
> n32 and n64? -gnuabi32n32n64 looks pretty crazy. |
56 |
> |
57 |
There is only one default ABI, so the toolchain should be named after |
58 |
that. But that does not mean the toolchain can't build for different ABIs |
59 |
|
60 |
-- |
61 |
Regards, |
62 |
Markos Chandras |