search for: landing1

Well, what I had in mind was actually something like the following: entry: result0 = invoke func0 to defer_block unwind landing0 landing0: landingpad result1 = invoke func1 to defer_block unwind landing1 landing1: landingpad br defer_block defer_block: result = phi [ result0, entry ], [ result1, landing0 ], [ null, landing1 ] ... This doesn't have landing pads with multiple predecessors like he said, but I don't think that would make much difference. The "defer block",...

...Santos <henrique.nazare.santos at gmail.com> wrote: > Well, what I had in mind was actually something like the following: > > entry: > result0 = invoke func0 to defer_block unwind landing0 > > landing0: > landingpad > result1 = invoke func1 to defer_block unwind landing1 > > landing1: > landingpad > br defer_block > > defer_block: > result = phi [ result0, entry ], [ result1, landing0 ], [ null, landing1 ] > ... > > This doesn't have landing pads with multiple predecessors like he said, > but I don't think that would...

On 4 November 2013 02:31, Henrique Santos <henrique.nazare.santos at gmail.com> wrote: > But the incoming value from the landing pad will always be null, won't it? > If so, just iterate through the predecessors and add the terminator as the > incoming value if it's an invoke instruction and add the null value it's > not. > Won't that work? > Note that the

...ail.com> wrote: > > Well, what I had in mind was actually something like the following: > > > > entry: > > result0 = invoke func0 to defer_block unwind landing0 > > > > landing0: > > landingpad > > result1 = invoke func1 to defer_block unwind landing1 > > > > landing1: > > landingpad > > br defer_block > > > > defer_block: > > result = phi [ result0, entry ], [ result1, landing0 ], [ null, > landing1 ] > > ... > > > > This doesn't have landing pads with multiple predecess...