> As tree merging really replaces trees it has to error on the side of not > merging while canonical type merging has to error on the side of "merging" > to make types alias.
OK, then the former won't be sufficient for Ada, there are known cases where producers and clients of a package cannot see the exact same tree for a type, so we definitely need optimistic merging here. > Btw, for the LTO_SET_PREVAIL can you introduce a LTO_SET_PREVAIL_EXPR > and use that for the fields that possibly can be expressions plus simply use > walk_tree for those (in case they are EXPR_P)? Please split that part out > as well. Yes, I can do that. -- Eric Botcazou
