Fix initialization style of objects allocated on the stack and member
objects in unit test to use the "Type Var(init list)" convention.
Details
- Reviewers
jhenderson probinson arichardson grimar jdenny - Commits
- rGe37bc5e49927: [NFC] [FileCheck] Reapply fix init of objects in unit tests
rL373755: [NFC] [FileCheck] Reapply fix init of objects in unit tests
rGedfb86969c1d: [NFC] [FileCheck] Fix init of stack objects in unit tests
rL373717: [NFC] [FileCheck] Fix init of stack objects in unit tests
Diff Detail
- Repository
- rL LLVM
Event Timeline
LGTM, since it makes things more readable. Beyond that, is there any particular motivation for this?
Several comments in https://reviews.llvm.org/D60389 asking to fix the same issue. Since there was already several instances of the issue in existing code I thought I'd fix them.
Sorry, but this change broke the build: http://lab.llvm.org:8011/builders/clang-x86_64-debian-fast/builds/18721
Please always run ninja check-all before committing.
I reverted this change in r373722.
I did ran check check-llvm-unit which runs this test. Is it possible that the unit test is not run using the compiler just built?
My bad, I can reproduce this, I might have just run ninja which of course does not do anything here.
Ok to commit this revised change? I double checked that I ran the unit tests this time and all tests pass.
For simple changes to fix a bot breakage, it's generally fine to just recommit the updated fix; people also like to see a comment in the commit log for the recommit that says something about what's different this time or why it's okay to recommit.