search for: _personality_

...ause the lifetimes of these hard registers ostensibly starts at the LandingpadInst, but for purposes of PHI lowering and Register Allocation they _must_ actually start at the beginning of the BasicBlock -- since that is where control flow will return to from the _Unwind_RaiseException / __gcc_personality_v0 calls, and it is the _Unwind_ and _personality_ functions that physically set those hard registers, not the "LandingpadInst". Somehow PHI lowering and register allocation need to be prohibited from using those hard registers for spill code at the beginning of a "landing pad bl...

...lifetimes of these hard registers ostensibly starts at the LandingpadInst, > but for purposes of PHI lowering and Register Allocation they _must_ actually > start at the beginning of the BasicBlock -- since that is where control flow will > return to from the _Unwind_RaiseException / __gcc_personality_v0 calls, > and it is the _Unwind_ and _personality_ functions that physically set those > hard registers, not the "LandingpadInst". > > Somehow PHI lowering and register allocation need to be prohibited from > using those hard registers for spill code at the beginning of a...

..."invoke-block" and the "landingpad-block", and if we do then isn't there the possibility of the register allocator spilling the contents of the exception registers from within the newly created block --- but this block won't ever get executed because the _Unwind_ / _personality_ functions will cause control flow to go directly to the block with the LandingpadInst ? If you really want to split a landingpad-edge won't you have to move the LandingpadInst up into the new block ? if this is true (and I seem to be making a lot of logic errors lately, so maybe rerea...

...starts at the >> LandingpadInst, >> but for purposes of PHI lowering and Register Allocation they >> _must_ actually >> start at the beginning of the BasicBlock -- since that is where >> control flow will >> return to from the _Unwind_RaiseException / __gcc_personality_v0 >> calls, >> and it is the _Unwind_ and _personality_ functions that physically >> set those >> hard registers, not the "LandingpadInst". >> >> Somehow PHI lowering and register allocation need to be prohibited >> from >> using those...