Displaying 2 results from an estimated 2 matches for "r168588".
Did you mean:
r168538
2012 Nov 17
0
[LLVMdev] Proposal: Enhance FileCheck's variable matching capabilities
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
2012 Nov 16
4
[LLVMdev] Proposal: Enhance FileCheck's variable matching capabilities
Hello,
FileCheck allows us to define match variables and use them on
subsequent lines. This is quite useful, but could be even more useful
if it was possible to use the variable later on the same line it
matched. For example, I would want to write this:
; CHECK: bic [[REG:r[0-9]+]], [[REG]], #3
But I currently can't because [[REG]] will only match a REG variable
defined on a _previous_