| 1 |
Hi all! |
| 2 |
|
| 3 |
Is it accepted for merge into kernel mainline for 3.2? |
| 4 |
Actualy this abi looks like n32 mips abi. |
| 5 |
|
| 6 |
PS why not merge all x86 abis into one keyword? because x86_32 x86_64 |
| 7 |
x86_x32 are only abis of x86. Also we dont have different keywords for |
| 8 |
different mips abis (64bit and 32bit ones) |
| 9 |
|
| 10 |
On Thu, 15 Sep 2011 15:34:06 -0400, Mike Frysinger wrote: |
| 11 |
> ive converted my system over to x86/amd64/x32 multilib for funs. but |
| 12 |
> i can |
| 13 |
> see how some people wont want all three all the time. so the |
| 14 |
> question is how |
| 15 |
> we want to make this available to users at the release/profile level. |
| 16 |
> |
| 17 |
> background: x32 is a new ABI that runs on 64bit x86_64 processors. |
| 18 |
> see [1]. |
| 19 |
> you'll need gcc-4.7+, binutils-2.21.50+, glibc-2.15+, and linux-3.2+. |
| 20 |
> |
| 21 |
> KEYWORDS wise, i'd like to avoid having to add "x32" everywhere. |
| 22 |
> instead, |
| 23 |
> reusing "amd64". only downside is the existing USE=amd64 behavior, |
| 24 |
> but we can |
| 25 |
> address that by making MULTILIB_ABIS a USE_EXPAND (i think this came |
| 26 |
> up before |
| 27 |
> with the portage multilib discussion). |
| 28 |
> |
| 29 |
> release wise, we could ship a single multilib stage (x86/amd64/x32) |
| 30 |
> and make |
| 31 |
> it easy to convert to a subset. that way we still need only one. |
| 32 |
> |
| 33 |
> other thoughts ? |
| 34 |
> -mike |
| 35 |
> |
| 36 |
> [1] https://sites.google.com/site/x32abi/ |
| 37 |
|
| 38 |
-- |
| 39 |
Best Regards, |
| 40 |
Alexey 'Alexxy' Shvetsov |
| 41 |
Petersburg Nuclear Physics Institute, Russia |
| 42 |
Department of Molecular and Radiation Biophysics |
| 43 |
Gentoo Team Ru |
| 44 |
Gentoo Linux Dev |
| 45 |
mailto:alexxyum@×××××.com |
| 46 |
mailto:alexxy@g.o |
| 47 |
mailto:alexxy@×××××××××××××.ru |
Archives