search for: recoverblock

...ll > to the handler followed by a jump to the %normalsucc > > A change that I'd consider preferable since it avoids the need for an > auxiliary switch in the non-EH code would be: > > - some new terminator along the lines of 'entercleanup %cleanupblock > recover to %recoverblock', rather than a plain branch, can target > cleanupblocks > > - the resume/unwind terminator that ends a cleanup would have any > number of additional successors, and just like the rule that the EH target > must match the %nextaction referenced on the cleanupblock, the non-EH...

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

...ll > to the handler followed by a jump to the %normalsucc > > A change that I'd consider preferable since it avoids the need for an > auxiliary switch in the non-EH code would be: > > - some new terminator along the lines of 'entercleanup %cleanupblock > recover to %recoverblock', rather than a plain branch, can target > cleanupblocks > > - the resume/unwind terminator that ends a cleanup would have any > number of additional successors, and just like the rule that the EH target > must match the %nextaction referenced on the cleanupblock, the non-EH...