bcardosolopes wrote:

> That would simplify the EHScopeStck handling significantly in CIR, but the 
> complexity would just be moved to the FlattenCFG pass, and this would mean we 
> were diverging from the classic codegen code structure.

I'm up for the tradeoff here, the lower level alternative will make code way 
harder to analyze.

https://github.com/llvm/llvm-project/pull/163849
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to