1 |
On 12/29/2013 09:48 PM, Michał Górny wrote: |
2 |
> Dnia 2013-12-29, o godz. 16:40:08 |
3 |
> Joshua Kinard <kumba@g.o> napisał(a): |
4 |
> |
5 |
>> On 12/28/2013 5:58 PM, Michał Górny wrote: |
6 |
>>> I've noticed today that mips uses the same CHOST value for all three |
7 |
>>> ABIs it supports: |
8 |
>>> |
9 |
>>> arch/mips/mips64/multilib/make.defaults:CHOST_o32="${CHOST}" |
10 |
>>> arch/mips/mips64/multilib/make.defaults:CHOST_n32=${CHOST} |
11 |
>>> arch/mips/mips64/multilib/make.defaults:CHOST_n64=${CHOST} |
12 |
>>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_o32="${CHOST}" |
13 |
>>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n32="${CHOST}" |
14 |
>>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n64="${CHOST}" |
15 |
>>> |
16 |
>>> [...] |
17 |
>> |
18 |
>> Matt can probably vouch for this better, but the only two ABIs affected by |
19 |
>> this are n32 and n64. mips[el]-unknown-linux-gnu implies a 32-bit |
20 |
>> big/little endian CHOST, which means the o32 ABI. |
21 |
>> mips64[el]-unknown-linux-gnu means either n32 or n64. So no change should |
22 |
>> be needed for o32-based installs. |
23 |
> |
24 |
> Just to be clear: |
25 |
> |
26 |
> profiles/arch/mips/mipsel/mips64el/multilib/make.defaults: |
27 |
> |
28 |
> CHOST="mips64el-unknown-linux-gnu" |
29 |
> |
30 |
> [...] |
31 |
> |
32 |
> CFLAGS_o32="-mabi=32" |
33 |
> CHOST_o32="${CHOST}" |
34 |
> |
35 |
> CFLAGS_n32="-mabi=n32" |
36 |
> CHOST_n32="${CHOST}" |
37 |
> |
38 |
> CFLAGS_n64="-mabi=64" |
39 |
> CHOST_n64="${CHOST}" |
40 |
> |
41 |
> So in this case, o32 actually uses mips64el-unknown-linux-gnu, unless |
42 |
> I'm missing something. |
43 |
> |
44 |
|
45 |
Yes all 3 ABIs use the same tuple. |
46 |
|
47 |
-- |
48 |
Regards, |
49 |
Markos Chandras |