Displaying 3 results from an estimated 3 matches for "normalsucc".
2015 May 19
2
[LLVMdev] RFC: New EH representation for MSVC compatibility
...ocks on non-EH
> paths.
>
> The smallest change to your proposal that comes to mind which would allow
> this would be:
>
> - a normal branch can target a cleanupblock
>
> - the resume/unwind terminator that ends a cleanup would have another
> optional target label (%normalsucc). The semantics would be that the EH
> edge to %nextaction would be taken if the cleanupblock were entered by an
> EH edge, and the normal edge to %normalsucc would be taken otherwise.
>
> - converting this to landingpads would manifest an i1 that would need
> to be set before br...
2015 May 19
2
[LLVMdev] RFC: New EH representation for MSVC compatibility
On Mon, May 18, 2015 at 8:40 PM, Joseph Tremoulet <jotrem at microsoft.com>
wrote:
> > I want to have separate normal and exceptional codepaths
>
> I assume you at least mean that's what you'll be doing in Clang's initial
> IR generation. Do you also mean to impose this as a restriction on other
> IR generators, and as a property that IR transformations must
2015 May 20
2
[LLVMdev] RFC: New EH representation for MSVC compatibility
...ocks on non-EH
> paths.
>
> The smallest change to your proposal that comes to mind which would allow
> this would be:
>
> - a normal branch can target a cleanupblock
>
> - the resume/unwind terminator that ends a cleanup would have another
> optional target label (%normalsucc). The semantics would be that the EH
> edge to %nextaction would be taken if the cleanupblock were entered by an
> EH edge, and the normal edge to %normalsucc would be taken otherwise.
>
> - converting this to landingpads would manifest an i1 that would need
> to be set before br...