1 |
On Thursday, September 15, 2011 16:12:00 Michał Górny wrote: |
2 |
> On Thu, 15 Sep 2011 15:34:06 -0400 Mike Frysinger wrote: |
3 |
> > KEYWORDS wise, i'd like to avoid having to add "x32" everywhere. |
4 |
> > instead, reusing "amd64". only downside is the existing USE=amd64 |
5 |
> > behavior, but we can address that by making MULTILIB_ABIS a |
6 |
> > USE_EXPAND (i think this came up before with the portage multilib |
7 |
> > discussion). |
8 |
> |
9 |
> Hrm, wouldn't that be more like x86 keyword? AFAICS the type sizes for |
10 |
> x86 and x32 would match. |
11 |
|
12 |
the sizeof(long) and sizeof(void*) are the same between x86 and x32. however, |
13 |
that's about the only thing. for example, x32 gets access to 64bit registers |
14 |
when working with 64bit types (long long) and the tuple is x86_64-pc-linux- |
15 |
gnu. in general, it seems to be closer to amd64 than x32. |
16 |
-mike |