llvm dev - Jun 2009 - [LLVMdev] Windows x64 JIT usability

What is the current state of the JIT on Windows x64?

I have noticed intermittent conversation about past incompatibility
due to the calling convention idiosyncrasies, as well as some
suggestion from last fall that it was targeted for a fix in the 2.5
timeframe, but see no definitive conclusion. Is this working in 2.5,
in trunk, or likely to be in trunk soon?

On Wed, Jun 3, 2009 at 6:29 PM, Jonathan Ragan-Kelley<jrk at
csail.mit.edu> wrote:
> What is the current state of the JIT on Windows x64?
Broken; at the very least, there's http://llvm.org/bugs/show_bug.cgi?id=3739
.

-Eli

----- Original Message ----- 
From: "Eli Friedman" <eli.friedman at gmail.com>
To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
Sent: Wednesday, June 03, 2009 6:36 PM
Subject: Re: [LLVMdev] Windows x64 JIT usability

> On Wed, Jun 3, 2009 at 6:29 PM, Jonathan Ragan-Kelley<jrk at
csail.mit.edu>
> wrote:
>> What is the current state of the JIT on Windows x64?
>
> Broken; at the very least, there's 
> http://llvm.org/bugs/show_bug.cgi?id=3739 .
>
sad...

in my case, otherwise I would have asked if anyone had benchmarked the 
SysV/AMD64 calling convention vs the Win64 calling convention...

I personally want to know what is faster, but can't find any benchmarks, nor
am that inclined in going through all the steps to get it working 
(installing a 64-bit windows, geting 64-bit compilation set up, and getting 
benchmarks to compare between Windows and Linux, ...).

but, alas, if anyone has tested this, I am hoping I can hear the results...


(sadly, I don't have anything available to accurately test Win64 on a 
Linux-based setup, but this could be technically more accurate than using 
Windows, since it would reduce the risk of OS-specific overhead 
differences...).

> -Eli
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>