search for: landindpadinst

Hi Peter, Thanks for pointing this out. Some us who are concerned with codegen have discussed the problem. Although the details aren't decided, you can be sure that at the MachineInstr level we won't have a landindpadInst to model liveness of exception values. Any physical registers set by the personality function will be considered live immediately after the call on the unwind path. -Andy On Aug 4, 2011, at 4:04 PM, Peter Lawrence wrote: > Chris, > it is goodness that the LandingpadInst will be...

Chris, it is goodness that the LandingpadInst will be pinned to the beginning of a BasicBlock,... except for the possibility of PHINode instructions that _must_ come even earlier.?. I can't exactly put my finger on what's going to go wrong with this, but it sure smells fishy... my current understanding is that the LandingpadInst will "define" some hard

...On Aug 4, 2011, at 4:16 PM, Andrew Trick wrote: > Hi Peter, > > Thanks for pointing this out. Some us who are concerned with > codegen have discussed the problem. Although the details aren't > decided, you can be sure that at the MachineInstr level we won't > have a landindpadInst to model liveness of exception values. Any > physical registers set by the personality function will be > considered live immediately after the call on the unwind path. > > -Andy > > On Aug 4, 2011, at 4:04 PM, Peter Lawrence wrote: > >> Chris, >> it...

...On Aug 4, 2011, at 4:16 PM, Andrew Trick wrote: > Hi Peter, > > Thanks for pointing this out. Some us who are concerned with > codegen have discussed the problem. Although the details aren't > decided, you can be sure that at the MachineInstr level we won't > have a landindpadInst to model liveness of exception values. Any > physical registers set by the personality function will be > considered live immediately after the call on the unwind path. > > -Andy > > On Aug 4, 2011, at 4:04 PM, Peter Lawrence wrote: > >> Chris, >> it...