en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected#f0dd12ec [x86] use zero-extending load of a byte outside of loops too (2nd try)The first attempt missed changing test files for tools(update_llc_test_checks.py).Original commit message:This implements the main suggested change from issue #56498.Using the shorter (non-extending) instruction with only-Oz ("minsize") rather than -Os ("optsize") is left as apossible follow-up.As noted in the bug report, the zero-extending load may haveshorter latency/better throughput across a wide range of x86micro-arches, and it avoids a potential false dependency.The cost is an extra instruction byte.This could cause perf ups and downs from secondary effects,but I don't think it is possible to account for those inadvance, and that will likely also depend on exact micro-arch.This does bring LLVM x86 codegen more in line with existinggcc codegen, so if problems are exposed they are more likelyto occur for both compilers.Differential Revision: https://reviews.llvm.org/D129775 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected Wed, 20 Jul 2022 01:25:41 +0000 Sanjay Patel <spatel@rotateright.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected#996873cd [UpdateTestChecks] Use a counter for unpredictable FileCheck variablesVariable captures such as `<MCInst #` can change based on unrelated changesto the LLVM backends, to avoid the generated test cases being differentuse an incrementing counter for variable names instead of using theactual value from the output file.This change may also be beneficial for some nameless IR variables(especially when combined with filtering of output), but for now I'verestricted this change to the obvious candidates (--asm-show-inst output).Reviewed By: MaskRayDifferential Revision: https://reviews.llvm.org/D125405 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected Thu, 12 May 2022 10:22:28 +0000 Alex Richardson <alexrichardson@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected#37a68497 [update_llc_test_checks] Use FileCheck captures for MCInst/MCReg outputTo avoid test churn when backends add/rename new instructions/registers,it makes sense to use FileCheck captures for the exact MCInst/Reg number.This is motivated by D125307, where I use --asm-show-inst to differentiatethe output for multiple instructions with the same mnemonic.This does not quite fix the churn issue yet: While files with the generatedchecks will be immune to the numbers changing, the update script teststill suffers from this problem since the number is encoded in theFileCheck variable name. I plan to address this in a follow-up patch.Reviewed By: MaskRayDifferential Revision: https://reviews.llvm.org/D125307 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected Thu, 12 May 2022 10:21:55 +0000 Alex Richardson <alexrichardson@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected#f4216592 [update_llc_test_checks] Baseline test for --asm-show-instTo avoid test churn when backends add/rename new instructions/registers,it makes sense to scrub the exact MCInst/Reg number.Differential Revision: https://reviews.llvm.org/D125305 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/asm-show-inst.ll.expected Thu, 12 May 2022 10:21:00 +0000 Alex Richardson <alexrichardson@google.com>