search for: exceptiondispatch

Hi all, I would like to propose a mechanism that would allow LLVM to fold null pointer checks into "nearby" memory operations, subject to runtime support. This is related to but not exactly the same as a proposal floated by Peter Collingbourne earlier [1]. The obvious use cases are managed languages like Java, C# and Go that require a null check on pointers before they're used in

...39;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' and the resume > that r...

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

...39;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' and the resume > that r...

...39;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' and the resume > that r...