search for: update_llc_test

...here is how often we should be using those scripts. Like many test-related issues, it comes down to personal judgement. It is of course easy to create test/CodeGen/*/* tests that pass regardless of whether the compiler breaks broken code regardless of whether the test CHECK lines are generated by update_llc_test.checks.py or not. I find it very helpful to have auto-generated CHECK lines that pick up any codegen change, but this can of course be problematic for very large test cases that are likely to see churn due to scheduling or regallloc changes. Being able to regenerate the CHECK lines and view the di...

...be using those scripts. > > Like many test-related issues, it comes down to personal judgement. It > is of course easy to create test/CodeGen/*/* tests that pass > regardless of whether the compiler breaks broken code regardless of > whether the test CHECK lines are generated by > update_llc_test.checks.py or not. > > I find it very helpful to have auto-generated CHECK lines that pick up > any codegen change, but this can of course be problematic for very > large test cases that are likely to see churn due to scheduling or > regallloc changes. Being able to regenerate the CHE...

Hello llvm-dev, On a recent code review I was asked to auto-generate assertion checks for my unit test. I wasn't aware that this was even possible. I am referring to the python `update` scripts under `utils` directory. My first reaction was wow! I found it very practical and useful. It saves you significant amount of time when writing a regression test. So I gave it a try. The generated

...>> >> Like many test-related issues, it comes down to personal judgement. It >> is of course easy to create test/CodeGen/*/* tests that pass >> regardless of whether the compiler breaks broken code regardless of >> whether the test CHECK lines are generated by >> update_llc_test.checks.py or not. >> >> I find it very helpful to have auto-generated CHECK lines that pick up >> any codegen change, but this can of course be problematic for very >> large test cases that are likely to see churn due to scheduling or >> regallloc changes. Being able t...

...; Like many test-related issues, it comes down to personal judgement. It >>> is of course easy to create test/CodeGen/*/* tests that pass >>> regardless of whether the compiler breaks broken code regardless of >>> whether the test CHECK lines are generated by >>> update_llc_test.checks.py or not. >>> >>> I find it very helpful to have auto-generated CHECK lines that pick up >>> any codegen change, but this can of course be problematic for very >>> large test cases that are likely to see churn due to scheduling or >>> regallloc c...

...-related issues, it comes down to personal judgement. It >>>> is of course easy to create test/CodeGen/*/* tests that pass >>>> regardless of whether the compiler breaks broken code regardless of >>>> whether the test CHECK lines are generated by >>>> update_llc_test.checks.py or not. >>>> >>>> I find it very helpful to have auto-generated CHECK lines that pick up >>>> any codegen change, but this can of course be problematic for very >>>> large test cases that are likely to see churn due to scheduling or >>...