aqjune added a comment. In D81678#2099444 <https://reviews.llvm.org/D81678#2099444>, @efriedma wrote:
> So I guess we've discussed the following alternatives so far: > > (snip) > > Maybe (1) is the least-bad; all the others compromise by making LLVM harder > to understand. We can make porting the clang tests easier by adding a cc1 > flag to turn off emitting frozen attributes, I guess (so instead of updating > the CHECK lines, you could just mechanically update the RUN line). In D81678#2099591 <https://reviews.llvm.org/D81678#2099591>, @eugenis wrote: > I agree that (1) is the easiest to work with and the least error-prone, and > that's what we must shoot for in the design. We could do (4) later as an > optimization. I agree. After going to (1) we can bring optimizations as a follow-up if it needed. I vote for the -cc1 option as a workaround. BTW, was there a case in the past that needed a massive updates in tests as well? I wonder how it was addressed at that time. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D81678/new/ https://reviews.llvm.org/D81678 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
