[LLVMdev] Proposal: Enhance FileCheck's variable matching capabilities

Eli Bendersky eliben at google.com
Sun Nov 18 05:53:27 PST 2012


On Fri, Nov 16, 2012 at 4:35 PM, Sean Silva <silvas at purdue.edu> wrote:
> If I understand correctly, the desire is to change the current
> behavior in a kind of subtle way. Is there some way you could
> instrument trunk's FileCheck to die if the old behavior is
> encountered, and use that to definitively find all tests which rely on
> the current behavior and migrate them (possibly to an interim
> solution) in preparation for the change in semantics?
>
> How much is the old (i.e. current) behavior used?
>

Running through the LLVM + Clang test suites, I found a single case in
test/CodeGen/PowerPC/i64_fp_round.ll, which uses a variable defined on
the same line (and thus actually referring to its previously defined
instance).

This isn't surprising, since the current behavior is IMHO somewhat
un-intuitive and not very useful.

Naturally, once the change in behavior occurs, this test will be
fixed, as well as any other tests that start failing as a result of
the change.

Eli



More information about the llvm-dev mailing list