amyk added a comment.
In D119136#3459738 <https://reviews.llvm.org/D119136#3459738>, @alanphipps
wrote:
> We've also been seeing failures in our downstream Arm compiler when running
> the Perennial C++14 compliance tests related to this change. Specifically,
> the tests expect a diagnostic to be issued when the lambda capture variable
> is outside of the lambda's {} scope. Another tests uses the lambda capture
> variable in a decltype-style return type which is also outside of the scope.
>
> Do these failures sound like what others have run into?
Hi, I would just like to express that I am also seeing these two issues on
Power, that are a result of the original patch (D119136
<https://reviews.llvm.org/D119136>) that @alanphipps has pointed out.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D119136/new/
https://reviews.llvm.org/D119136
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
