Also, and I don't think this is an official standpoint, but I've heard prominent figures within the V8/Chromium teams express reluctance to support x86-64 code generation anytime soon, since it would roughly double the amount of memory needed for V8 applications (it uses *a lot* of pointers), and is not currently necessary to support at all, since all major operating systems for x86-64 CPUs can run x86 code just fine.
Look into your heart and ask yourself the question: Am I wanting to compile V8 for x86-64 for any other reason than vanity, pride, and cosmetics? ;-) Joking aside, it would be "nice" with a native x86-64 version of V8, but I don't believe it's a priority for the Google teams. V8 is open source, however, so if you feel like it, I'm sure it would be considered a very valuable addition to the code base. :-) Sincerely, Simon 2008/9/29 Jey Kottalam <[EMAIL PROTECTED]>: > > On Mon, Sep 29, 2008 at 12:54 PM, <[EMAIL PROTECTED]> wrote: >> >> Are there plans to fix that so the code can build properly on 64 >> bit? It's a pretty big limitation to not be able to link against it >> when the rest of your code is 64 bit compat. >> > > I think the V8 code generator only supports ia32 and ARM targets, and > there is no support in the code generator for x86-64 nor an > interpreted mode. > > -Jey Kottalam > > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
