search for: update_test_checks

...oopStrengthReduce/uglygep.ll (RUN: opt < %s -lcssa -loop-reduce -S | FileCheck %s). Any thoughts on how to fix these 30-35 tests? Manually convert them to LCSSA form and update the CHECK lines? Seems tricky, especially for somebody without much experience with these passes. Some of these do use update_test_checks, but some do not. Another option is to add an option to disable running LCSSA, but that doesn't seem right. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201109/15d54ad6/attachment.html>

...s doc. [r324004](http://reviews.llvm.org/rL324004). * The sigil for machine IR physical registers is now `$` rather than `%`. [r323922](http://reviews.llvm.org/rL323922). * Support has been added to dsymutil for generating Apple accelerator tables. [r323655](http://reviews.llvm.org/rL323655). * `update_test_checks.py` and `update_llc_test_checks.py` have been refactored to share common code. [r323718](http://reviews.llvm.org/rL323718). * A scheduling model has been added for the Exynos M3. [r323773](http://reviews.llvm.org/rL323773). * A new extension is now supported, linker options can be passed from the...

...red by Rust. [r324426](http://reviews.llvm.org/rL324426). * Code generation for Armv8.2-A FP16 has been added. [r324321](http://reviews.llvm.org/rL324321). * The MergeICmps pass is now enabled by default. [r324465](http://reviews.llvm.org/rL324465). * `utils/update_llc_test_checks.py` and `utils/update_test_checks.py` have been updated to share more code. [r324803](http://reviews.llvm.org/rL324803). ## Clang commits * The `trivial_abi` attribute has been added. This indicates the annotated C++ class/struct/union to be passed or returned using the C ABI for the underlying type. [r324269](http://reviews.llvm...

...Summer of Code have closed, but the [list of new project ideas](http://lists.llvm.org/pipermail/llvm-dev/2016-March/097380.html) from Philip Reames is a good starting point for anybody looking for a way to get stuck in to making impactful contributions to LLVM. ## LLVM commits * A new utility, `update_test_checks.py` was added to update opt or llc test cases with new FileCheck patterns. [r264357](http://reviews.llvm.org/rL264357). * Non-power-of-2 loop unroll count pragmas are now supported. [r264407](http://reviews.llvm.org/rL264407). * The NVPTX backend gained a new address space inference pass. [r26391...

...match with any metadata node that has the same number of operands, deferring a mismatch report to some later CHECK line, but due to the DAG part continuing to match with previous lines. Unfortunately, most tests we have do not even use placeholders for metadata nodes, including those generated by update_test_checks.py. I looked into improving the script in this regard, but its implementation is function-centric, making it difficult to add module-level placeholders. As a result, I estimate that I had to invest about twice the time to update/fix tests than writing the code changes themselves. Due to my experie...

Am Mi., 24. Juni 2020 um 00:37 Uhr schrieb David Blaikie <dblaikie at gmail.com>: > I'm pretty change averse - and am in this case (but doesn't mean other folks won't be in favor and doesn't mean it isn't worth trying, etc - but if it were up to me, at the moment, I'd decline) That's understandable. New features also come with a cost that they need to recoup

Hello LLVM community, For testing IR passes, LLVM currently has two kinds of tests: 1. regression tests (in llvm/test); .ll files invoking opt, and matching its text output using FileCheck. 2. unittests (in llvm/unittests); Google tests containing the IR as a string, constructing a pass pipeline, and inspecting the output using code. I propose to add an additional kind of test, which I call