sepavloff added a comment.

In, @pcc wrote:

> > If the backend will be changed so that it will not depend on IR type names
> Are you referring to If so it seems to me 
> that this should be a cc1 flag that defaults to whether `-flto=thin` is 
> passed. In any case it seems like a bad idea to deliberately generate 
> different code depending on whether we were compiled with NDEBUG.

No, I try to implement alternative approach, to solve the problem targeted in If  IR type names are only for human 
readability, than using them in opaque type resolution does not look 
reasonable. Probably, more correct way is to make type merge only as a side 
effect of merge of other entities, which may have "real" names, that is 
functions and variables.

  rC Clang

cfe-commits mailing list

Reply via email to