similar to: Win64 problems

Hi all I'm wondering if it would be possible to run Wine on Win64 ("x64") to allow Win16 apps to be run? Preferably a native 64-bit binary, using mostly native DLLs. (Services for Unix / Subsystem for Unix based Applications might help for getting Wine compiled) It might be a great way to get more users and developers for Wine. Regular Windows releases of the DirectX 10 DLL's

Hi Chandler, There were five SEH releated patches posted in two threads in the last days. Two different patches in Martell e-mail starting this thread: the win64 seh (llvm) and the register names Three more related SEH patches in another thread: one for win64 seh clang, one for MinGW toolchain and another for unreachable prologue. To clarify and allow proper reviews for the different patches I

In summary we have no less than six patches required to support Win64 SEH MinGW. The first five could be committed after review and LGTM but the last one also requires Ray Donnelly approval. Please comment in the Phabricator so the comments would be kept in context. 'unreachable' trap http://reviews.llvm.org/D3417 Win64 SEH (LLVM) http://reviews.llvm.org/D3418 Win64 SEH (clang)

On Thu, Jul 30, 2009 at 5:32 PM, Peter Shugalev<peter at shugalev.com> wrote: > Hello! > > I've just tried generating Win64 code and the result is not that good. > > First of all, XMM registers are saved without reason to do so. Not only > this slows the performance but leads to random crashes too. XMMs are > stored to the stack with MOVAPS instruction which requires

+LLVMdev On Aug 4, 2012, at 9:45 AM, João Matos wrote: > Charles Davis did a lot of work on Win64 SEH support in LLVM, check commits r131652-r132880. > > As I haven't tested it yet, what exactly is broken? It's not finished yet. All the stuff for assembly code that uses Win64 EH is done, but not the code-gen-side stuff (cf. Win64Exception class in CodeGen). I was about to

Hi all, In my MSVC-compiled project I am using MCJIT to run some generated code. I faced that in case of Win64 ('x86_64-pc-win32-elf') __try/__except block doesn't work - the stack can not be unwound. I have found that the only way to fix it is implementing my own *registerEHFrames* function of the Memory Manager (but I'm not sure this helps). Maybe someone had a success solving

LLVM3.8 version. https://bugs.llvm.org//show_bug.cgi?id=24233. The example can catch exception. But I use my own code for testing, CustomEHMemoryManager allocated memory address is very large, allocateCodeSection, allocateDataSection assigned address (more than 32 bit address space) is getting smaller and smaller. Cause registerEHFrames to fail. 3.9.1 or 4.0.0 version has been supported on win

Great! Are there other issues I should be aware of? Félix Le 2010-11-25 à 07:43:23, Anton Korobeynikov a écrit : > Hello Felix > >> I have a project in mind that involves using the JIT for a few targets (x86 >> and x86_64 processors on Mac OS, Linux and Windows). However, there is an >> open bug that says LLVM generates incorrect code for Win64. >> Eli's last

Hello guys, I have a project in mind that involves using the JIT for a few targets (x86 and x86_64 processors on Mac OS, Linux and Windows). However, there is an open bug that says LLVM generates incorrect code for Win64. Eli's last comment on the bug, however, says that it appears to be fixed. I don't have a Win64 box to test it. Can someone confirm that it now works (or still

Hi again, Can anyone tell me about the state of Win64 exceptions? I've noticed that there are a good few related patches since the release of 3.1. Is it working now? Is it likely 3.2 will support Win64 exceptions? Cheers. - Manu -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello > I don't know. I feel reluctant to generate different IRs for Win32 and > for Win64. Unfortunately, you should. Think about differences and between _Complex type and struct {double, double}. >From LLVM's point of view these are same types, however many ABIs have special rules for passing / returning _Complex, this is possible to handle in frontend only. > Since the C

I have an old conferencing app that uses theora and I'm building it for win64. libthora 1.1 builds just fine, but libtheora 1.0 has errors related to assembly code when building for x64. I've tried using 1.1, but the video does not look right -- the clients all generate their own first 3 packets instead of sending them over the network since they assume they are all on the same version

Hello, I think I've found a bug in the calling convention support for X86-64/ Win64. It doesn't correctly save and restore the XMM registers in the function prolog/epilog. (The problem only exists on Win64, since Linux and Mac OS use calling convention in which these registers are volatile and not callee-saved.) X86RegisterInfo::getCalleeSavedRegs() when called for a Win64

Thanks, Anton! I didn't know about exceptions like _Complex that you mentioned. The only way to support them is to place the burden of correct parameter passing on the front-end, I understand that now. So, today I created a new transformation pass that makes sure that LLVM IR, which works alright with the default Win32 calling conventions, also plays nice with Win64 code within the limited

On 30-Jul-09, at 8:54 PM, Eli Friedman wrote: > On Thu, Jul 30, 2009 at 5:32 PM, Peter Shugalev<peter at shugalev.com> > wrote: >> Though the most problematic stuff is the lack of 'shadow zone' >> support >> in Win64 ABI. Or maybe I haven't figured out how to turn this on. In >> Win64 any function can treat 32 bytes of stack (RSP+08h..RSP+28h

Hello! I've just tried generating Win64 code and the result is not that good. First of all, XMM registers are saved without reason to do so. Not only this slows the performance but leads to random crashes too. XMMs are stored to the stack with MOVAPS instruction which requires 16-byte alignment which is not always the case. lli.exe (built in debug mode) randomly crashes on some simple

Hi Peter, The attached patch is a workaround for the XMM misalignment issue. Basically it uses the fallback method of saving and restoring registers on the stack, which does work correctly with alignment. If I recall correctly it also doesn't save any registers unnecessarily, but I could be wrong about that. Anyway, it's hack, but if all you want for now is to be able to work with Win64

For help: Llvm generated instruction calls a function (extern), the function will have a SEH exception (EXCEPTION_ACCESS_VIOLATION), But JIT can not capture the exception of the EXCEPTION_ACCESS_VIOLATION. I saw Bug 24233. EXCEPTION_ACCESS_VIOLATION exception cannot be captured after modification. How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64 ? haifeng.qin at wellintech.com

Hello Felix > I have a project in mind that involves using the JIT for a few targets (x86 > and x86_64 processors on Mac OS, Linux and Windows). However, there is an > open bug that says LLVM generates incorrect code for Win64. > Eli's last comment on the bug, however, says that it appears to be fixed. > I don't have a Win64 box to test it. Can someone confirm that it now

Nobody? Is this basically dead? Won't happen? In progress? :/ On 12 September 2012 18:53, Manu <turkeyman at gmail.com> wrote: > Hi again, > > Can anyone tell me about the state of Win64 exceptions? > I've noticed that there are a good few related patches since the release > of 3.1. Is it working now? > Is it likely 3.2 will support Win64 exceptions? > >