search for: regallloc

...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 diff is also incredibly helpful when rebasing or moving a patch between different branches. My policy for test/Codegen/RISCV is to use update_llc_test_checks.py wherever possible, except in cases where there are so many CHECK lines on...

...t 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 diff is also incredibly helpful when rebasing or moving a patch > between different branches. > > My policy for test/Codegen/RISCV is to use update_llc_test_checks.py > wherever possible, except in cases where there are...

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

...ted 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 diff is also incredibly helpful when rebasing or moving a patch >> between different branches. >> >> My policy for test/Codegen/RISCV is to use update_llc_test_checks.py >> wherever possible, except in c...

...te_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 diff is also incredibly helpful when rebasing or moving a patch >>> between different branches. >>> >>> My policy for test/Codegen/RISCV is to use update_llc_test_checks.py >>> wherever p...

...y 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 diff is also incredibly helpful when rebasing or moving a patch >>>> between different branches. >>>> >>>> My policy for test/Codegen/RISCV is to use update_llc_test_checks.py >&gt...