search for: zxtb

.../* Should almost never emit this. */ p1 = r4 /* Should almost never emit this. */ .. .. p0 = or(p1, p0) ***** The CHECK tags I have are ; CHECK: [[IntReg0:r[0-9]+]] = memb //IntReg0 is r3 ; CHECK: [[IntReg1:r[0-9]+]] = memb //IntReg1 is r4 ; CHECK-NOT: {{r[0-9]+}} = zxtb([[IntReg1]]) //Ensure no zxtb instructions exist between the loads and their uses. ; CHECK-NOT: {{r[0-9]+}} = zxtb([[IntReg0]]) ; CHECK: [[PredReg0:p[0-3]+]] = [[IntReg0]] // <--- [1] ; CHECK: [[PredReg1:p[0-3]+]] = [[IntReg1]] // <--- [2] ; CHECK: or([[PredReg1]], [[PredReg0]]) When I w...

...p1 = r4 /* Should almost never emit this. */ > .. > .. > p0 = or(p1, p0) > > ***** > The CHECK tags I have are > ; CHECK: [[IntReg0:r[0-9]+]] = memb //IntReg0 is r3 > ; CHECK: [[IntReg1:r[0-9]+]] = memb //IntReg1 is r4 > ; CHECK-NOT: {{r[0-9]+}} = zxtb([[IntReg1]]) //Ensure no zxtb > instructions exist between the loads and their uses. > ; CHECK-NOT: {{r[0-9]+}} = zxtb([[IntReg0]]) > ; CHECK: [[PredReg0:p[0-3]+]] = [[IntReg0]] // <--- [1] > ; CHECK: [[PredReg1:p[0-3]+]] = [[IntReg1]] // <--- [2] > ; CHECK: or([[PredReg1]]...

On Thu, Sep 13, 2012 at 1:14 PM, Pranav Bhandarkar <pranavb at codeaurora.org>wrote: > Just adding to the clamor for FileChecks ability to pattern match > out-of-order (match for mere presence); Just in the last 2 weeks, I have > come across at least a couple instances when I was unable to add small unit > tests to the testsuite because of this deficiency in FileCheck. Also, I

Just adding to the clamor for FileChecks ability to pattern match out-of-order (match for mere presence); Just in the last 2 weeks, I have come across at least a couple instances when I was unable to add small unit tests to the testsuite because of this deficiency in FileCheck. Also, I agree with Krzysztof about the lack of any real recurring overhead. Can this feature please be added to