search for: maybeoverriden

Hi Andy, Thanks for replying, responses inline below: On Fri, Feb 19, 2016 at 11:12 AM, Andrew Trick <atrick at apple.com> wrote: > This clearly doesn't need operand bundles, but using an intrinsic > would permit special code motion semantics. It could be hoisted and > merged with other traps, but the condition could never be widened > beyond the union of the original

...eading. It's probably cleaner to adhere to the rule that unwinding > can only resume in a landing pad. Ok. > I understand your problem. I was ignoring an aspect of analyzing the > unwind path and the fact the LLVM could make assumptions about where > control will resume. > > mayBeOverriden makes sense. I would think that the symbol at the deopt > call site needs to be marked mayBeOverriden. Ok. I'll probably split off an "introduce a `interposable` function attribute" into an independent review (I think re-using a linkage type for this will be somewhat of a hack)....

On Wed, Feb 17, 2016 at 8:53 PM, Philip Reames <listmail at philipreames.com> wrote: > I think you're jumping ahead a bit here. I'm not sure the semantics are > anywhere near as weird as you're framing them to be. :) I now think this weirdness actually does not have to do anything with guard_on or bail_to_interpeter, but it has to do with deopt bundles itself. Our