search for: wineh

...sn't seem to have a switch from code, only from the llc command line. Unless I'm missing something obvious, this will always screw up debug info on Windows 32bits. The check in code to enable this calls: bool usesWindowsCFI() const { return ExceptionsType == ExceptionHandling::WinEH && (WinEHEncodingType != WinEH::EncodingType::Invalid && WinEHEncodingType != WinEH::EncodingType::X86); } Where EncodingType::X86: //Windows x86, uses no CFI, just EH tables The comment seems to imply there are EH tables for i386 Windows, however I ca...

Have got anything started with the dispatchblock plan? From: Reid Kleckner [mailto:rnk at google.com] Sent: Wednesday, May 13, 2015 1:15 PM To: Kaylor, Andrew Cc: David Majnemer <david.majnemer at gmail.com> (david.majnemer at gmail.com); LLVM Developers Mailing List Subject: Re: [WinEH] A hiccup for the Windows C++ exception handling On Wed, May 13, 2015 at 11:03 AM, Kaylor, Andrew <andrew.kaylor at intel.com<mailto:andrew.kaylor at intel.com>> wrote: So there are two issues here. 1) We need a better way to figure out which blocks should be in which handlers and pro...

...tion-tests', and we can arrange to auto-detect it if it gets checked out under llvm/projects/ and set up a test suite. On Thu, May 28, 2015 at 1:35 PM, Joseph Tremoulet <jotrem at microsoft.com> wrote: > Hi, > > > > Have any decisions been made on where to put executable WinEH tests? > Wherever they go, would it be helpful if I were to add some C++EH and/or > SEH tests pulled from MSVC's test suite, since compatibility is the goal > here? > > > > Thanks > > -Joseph > > > > *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-b...

Hi, Have any decisions been made on where to put executable WinEH tests? Wherever they go, would it be helpful if I were to add some C++EH and/or SEH tests pulled from MSVC's test suite, since compatibility is the goal here? Thanks -Joseph From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Reid Kleckner Sent: Tuesday,...

...orking these changes into trunk to establish a working baseline, even knowing that parts of this are going to be redesigned? -Andy From: Reid Kleckner [mailto:rnk at google.com] Sent: Wednesday, May 13, 2015 2:16 PM To: Kaylor, Andrew; David Majnemer Cc: LLVM Developers Mailing List Subject: Re: [WinEH] A hiccup for the Windows C++ exception handling Basically, I'm trying to come up with a good design doc with David right now so I can mail it out. :) On Wed, May 13, 2015 at 1:43 PM, Kaylor, Andrew <andrew.kaylor at intel.com<mailto:andrew.kaylor at intel.com>> wrote: Have got an...

I've been looking at compilation time issues in the LICM pass, and it looks to me like colorEHFunclets() is probably being called a lot more often than it needs to be for functions that have Windows EH personality functions. For one thing, the funclet coloring is happening when computeLoopSafetyInfo() is called from LoopIdiomRecognize and LoopUnswitch but those passes don't use the

...t occurs to me that we should probably move the cppeh outlining tests, since they aren't actually X86-specific. We should probably also add an ARM+Windows run line to them. I'm torn between whether they should go in the test/CodeGen/CPP folder or in a new test/CodeGen/Win (or test/CodeGen/WinEH) folder. Thoughts? -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150303/afcde927/attachment.html>

I've been working recently to get the following test case working for an x86_64-pc-windows-msvc target. void test1() { try { try { throw 1; } catch(...) { throw; } } catch (...) { } } I committed a patch earlier in the week to get the WinEHPrepare pass to produce IR that I thought was sufficient, but as I mentioned in the review I was still seeing runtime errors when executing a program compiled with this code. I have since figured out why the program crashes at runtime, but fixing it is going to be a bit tricky. It has to do with s...

...t part of the work > to be done here 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. > 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 probl...

...eems 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 pla...

https://llvm.org/docs/ExceptionHandling.html#wineh > No variables live in to or out of the funclet can be allocated in registers. I don't think this is quite true. though it might be a useful simplification. Obviously it is true for volatile registers, but I believe the funclet receives a CONTEXT with the nonvolatiles restored. Obviously...

...di Amini <mehdi.amini at apple.com> wrote: > > Can you elaborate why? I’m curious. > The con of proposal c was that many passes would need to learn about many region intrinsics. With tokens, you only need to teach all passes about tokens, which they should already know about because WinEH and other things use them. With tokens, we can add as many region-introducing intrinsics as makes sense without any additional cost to the middle end. We don't need to make one omnibus region intrinsic set that describes every parallel loop annotation scheme supported by LLVM. Instead we would...

Hi Reid and David, I just wanted to give you a heads up that I'm currently working on a problem where the WinEHPrepare outlining code stumbles and asserts while cloning code that references extracted landing pad values via PHI nodes that are in intermediate blocks that aren't being cloned. The test I'm looking at fails with an assertion claiming that llvm.eh.begincatch was called twice inside a hand...

Hi, All I am trying to implement a llvm backend. But I encountered the following problem when running the backend: "Fatal error: error in backend: WinEH not implemented for this target" This error is triggered by function processFunctionBeforeFrameFinalized() defined in class TargetFrameLowering. Can anyone help? Thanks a lot! Zhiguo [cid:image001.jpg at 01D50970.C9344210] -------------- next part -------------- An HTML attachment was sc...

Hi, I have a function with: attributes #2 = { "no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-leaf" } Yet when compiling it generates: https://gist.github.com/carlokok/7c3c98d2fd8c966671f40a5ad94f19d3 (Note how it checks fFinalizer before setting up ebp). It also has a: .loc 36 195 7 prologue_end before this happens How can I get llvm to do the frame

...true, it is possible, but I don't think it fits very well in our current model and CFG. Given that it doesn't fit the model, I don't think it's helpful to try to explain this in the documentation. The document is intended to aid LLVM developers who don't particularly care about WinEH but want to understand it enough to avoid breaking it. If we wanted to exploit this optimization opportunity, we would clip funclets out of the CFG and add edges from invokes to all possible catchret destinations. Then the CSR mask of the call would naturally provide the right register allocation...

...sted landing pads) and we wouldn’t need to track it at all. -Andy From: Reid Kleckner [mailto:rnk at google.com] Sent: Friday, April 10, 2015 4:06 PM To: Kaylor, Andrew Cc: David Majnemer <david.majnemer at gmail.com> (david.majnemer at gmail.com); LLVM Developers Mailing List Subject: Re: [WinEH] Cloning blocks that reference non-cloned PHI nodes Sounds reasonable. Honestly, we've been having some serious whiteboard discussions about how to get out of doing all this selector pattern matching. I think that's basically the most fragile part of winehprepare, and if we can add some ne...

Hi, On Thu, 28 Jul 2016 09:32:18 -0700 Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think David and I are probably the most familiar with how WinEH works in > LLVM, but I don't think either of us has time to prepare a talk for the dev > meeting. I'm trying to prepare a talk on supporting the MS debug info > format in LLVM this year. That said, I'll definitely have time to answer > questions in person. It might be worth...

...di.amini at apple.com>> wrote: >> Can you elaborate why? I’m curious. >> >> The con of proposal c was that many passes would need to learn about many region intrinsics. With tokens, you only need to teach all passes about tokens, which they should already know about because WinEH and other things use them. >> >> With tokens, we can add as many region-introducing intrinsics as makes sense without any additional cost to the middle end. We don't need to make one omnibus region intrinsic set that describes every parallel loop annotation scheme supported by LLVM...

I think David and I are probably the most familiar with how WinEH works in LLVM, but I don't think either of us has time to prepare a talk for the dev meeting. I'm trying to prepare a talk on supporting the MS debug info format in LLVM this year. That said, I'll definitely have time to answer questions in person. It might be worth setting up a BoF to...