search for: dispatchblock

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

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

...ws 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 anything started with the dispatchblock plan? From: Reid Kleckner [mailto:rnk at google.com<mailto:rnk at google.com>] Sent: Wednesday, May 13, 2015 1:15 PM To: Kaylor, Andrew Cc: David Majnemer <david.majnemer at gmail.com<mailto:david.majnemer at gmail.com>> (david.majnemer at gmail.com<mailto:david.majnemer at gm...

...t; You could consider 'filter' (or 'filterblock') for 'catchblock', since > conceptually it plays the role of a filter (typically one which consults > type information; I've seen such things called "typetestfilter" before). > Or 'dispatch'/'dispatchblock'/'exceptiondispatch'/'dispatchexception' > (isn't that what Clang names the blocks it creates for the explicit > dispatch code?); 'catchendblock' would then be something like > 'unwinddispatch' or 'continuedispatch' or 'resumedispatch'...

On Mon, May 18, 2015 at 12:03 PM, Joseph Tremoulet <jotrem at microsoft.com> wrote: > Hi, > > > > Thanks for sending this out. We're looking forward to seeing this come > about, since we need funclet separation for LLILC as well (and I have > cycles to spend on it, if that would be helpful). > > > > Some questions about the new proposal: > > >

...t; You could consider 'filter' (or 'filterblock') for 'catchblock', since > conceptually it plays the role of a filter (typically one which consults > type information; I've seen such things called "typetestfilter" before). > Or 'dispatch'/'dispatchblock'/'exceptiondispatch'/'dispatchexception' > (isn't that what Clang names the blocks it creates for the explicit > dispatch code?); 'catchendblock' would then be something like > 'unwinddispatch' or 'continuedispatch' or 'resumedispatch'...

...t; You could consider 'filter' (or 'filterblock') for 'catchblock', since > conceptually it plays the role of a filter (typically one which consults > type information; I've seen such things called "typetestfilter" before). > Or 'dispatch'/'dispatchblock'/'exceptiondispatch'/'dispatchexception' > (isn't that what Clang names the blocks it creates for the explicit > dispatch code?); 'catchendblock' would then be something like > 'unwinddispatch' or 'continuedispatch' or 'resumedispatch'...