kbelochapka wrote: > e.g., #220053 > > In particular anything ABI influencing shouldn't be buried in an LTO specific > config
Hi @arsenm, Could you please elaborate on what, in your opinion, needs to be done? How can we ensure that removing any field from `lto::Config` or `llvm::TargetOptions` serialization does not eventually affect code generation? For example, let's assume that `lto::Config` currently contains a member `XXX` that has no impact on code generation, so we decide to remove it from serialization. However, after some time and several subsequent commits, someone may start using `XXX` during code generation. In that case, the serialization format would silently become incomplete, potentially leading to correctness issues. What mechanism or process would prevent such regressions? https://github.com/llvm/llvm-project/pull/219894 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
