This case will show furture optimization of add-imm & sub-imm.
Diff Detail
Event Timeline
llvm/test/CodeGen/ARM/armv6-add-sub-imm.ll | ||
---|---|---|
1 | Have you considered removing armv6- from the filename? If people want to test armv7-, they can simply add another RUN line. BTW, you may consider llvm/utils/update_llc_test_checks.py, which can make test updating easy. | |
6 | ; CHECK-LABEL: sub0: | |
17 | Add -NEXT: whenever appropriate |
llvm/test/CodeGen/ARM/add-sub-imm.ll | ||
---|---|---|
4 ↗ | (On Diff #278379) | ;; probably works better. In the future, we can ask update_llc_test_checks.py to always retain ;; comments. (There is some intricate logic retaining ; comments) |
Although I don't mind at all new tests being added, in this case I am really wondering if the code paths are not exercised by existing tests. And also reading the description:
This case will show furture optimization of add-imm & sub-imm.
I am wondering what these future optimizations are and if these tests should simply go in with that then?
I expect this test will show improvements in
https://reviews.llvm.org/D83745
https://reviews.llvm.org/D84100
I hope this test case first be merged, then the above two patches will affect this test.
Have you considered removing armv6- from the filename?
If people want to test armv7-, they can simply add another RUN line.
BTW, you may consider llvm/utils/update_llc_test_checks.py, which can make test updating easy.