1 |
On Friday 05 October 2012 10:28:45 Paweł Hajdan, Jr. wrote: |
2 |
> This is the case with dev-lang/v8: it doesn't build on x32 |
3 |
> (<https://bugs.gentoo.org/423815>), and upstream said they *won't* |
4 |
> support x32 |
5 |
> (<https://groups.google.com/d/msg/v8-users/c-_URSZqTq8/7wHl095t2CMJ>). |
6 |
|
7 |
i think you misread. they have no current plans to support it. there are (or |
8 |
at least were) people from intel working on it, although i don't know how far |
9 |
they got. |
10 |
|
11 |
> Note that with v8 it's not just about getting v8 itself to compile, but |
12 |
> also making it generate correct JIT code on x32, which would require |
13 |
> substantial changes to v8 code (in fact, a whole new 40K arch port, see |
14 |
> the discussion linked to above). |
15 |
|
16 |
i think upstream is mistaken there for various reasons. (1) it probably makes |
17 |
no sense to try and re-use the ia32 port for x32 and (2) the x32 and x64 port |
18 |
will most likely share a vast majority of code. after all, the entire |
19 |
register set is available to you in x32 the same as it is in x64. |
20 |
|
21 |
> Should dev-lang/v8 get p.masked on x32 profile, or is there some better |
22 |
> way to handle it? |
23 |
|
24 |
p.mask it for now makes sense if there is no portable/C implementation we can |
25 |
fall back onto |
26 |
-mike |