News for hackers. Stuff that matters.
Re:Visual Studio 2013 by yuhong on Monday June 03, 2013 @07:31PM (#5816799)
For one thing, I don't think their JIT produces code that properly follows the Windows x64 ABI yet. It really should be disabled in 64-bit builds until they do.
Re:Visual Studio 2013 by terrymah on Monday June 03, 2013 @10:33PM (#5817345)
Following the ABI is only an issue at module boundaries. If you control every callsite of a function, you can invent whatever calling convention you want.
Re:Visual Studio 2013 by yuhong on Tuesday June 04, 2013 @03:03AM (#5818071)
But you still need the function tables and follow prolog/epilog conventions with x64 for SEH to work.
Re:Visual Studio 2013 by jlgreco on Monday June 03, 2013 @07:40PM (#5816825)
Their stated reason for de-prioritizing 64-bit builds wasn't technical; rather they say they don't have the manpower to do both. Perhaps the manpower issue is that they don't have enough people to work on the JIT issues on x64 and do everything else, but I do not believe they specified.