search for: x86winehst

...e seems like it will remain relevant even after the current redesign comes to fruition and even what won't remain relevant looks like it will be interesting as input to the redesign. Have either of you (Reid and David) looked closely at the 32-bit C++ EH case? I saw the preliminary support in X86WinEHState, and I'm currently working on addressing the problem described in the FIXME comment there. I had been under the impression that 32-bit C++ EH was pretty much just a matter of making the equivalent of the xdata tables accessible via the stack and everything would more or less fall into place...

...Maybe that makes more sense. I was kind of trying to put aside WinEHPrepare issues and tackle 32-bit state numbering myself, but I kept getting dragged back to outlining problems. Have either of you (Reid and David) looked closely at the 32-bit C++ EH > case? I saw the preliminary support in X86WinEHState, and I’m currently > working on addressing the problem described in the FIXME comment there. I > had been under the impression that 32-bit C++ EH was pretty much just a > matter of making the equivalent of the xdata tables accessible via the > stack and everything would more or less...

...s.cpp for Release+Asserts build llvm[3]: Compiling X86VZeroUpper.cpp for Release+Asserts build llvm[3]: Compiling DwarfExpression.cpp for Release+Asserts build llvm[3]: Compiling LoopUnswitch.cpp for Release+Asserts build llvm[3]: Compiling DwarfFile.cpp for Release+Asserts build llvm[3]: Compiling X86WinEHState.cpp for Release+Asserts build llvm[3]: Compiling InstCombineLoadStoreAlloca.cpp for Release+Asserts build llvm[3]: Compiling DwarfStringPool.cpp for Release+Asserts build llvm[3]: Compiling LowerAtomic.cpp for Release+Asserts build llvm[3]: Building Release+Asserts Archive Library libLLVMX86Code...