Displaying 5 results from an estimated 5 matches for "negativestrid".
Did you mean:
negativestride
2007 Nov 26
2
[LLVMdev] Problem with regression tests using stderr
...hen.
Then we can look at removing the associated code from llvm.exp and fixing
the bug. This will take a while though, at it exposes a large number of
failures that are currently hidden.
> If you want to catch stderr, there is one test doing that:
>
> Analysis/ScalarEvolution/2007-07-15-NegativeStride.ll:
>
> ; RUN: llvm-as < %s | opt -analyze -scalar-evolution 2>&1 | grep
> "Loop bb: 100 iterations"
2>&1 doesn't evoke the desired behavior; the RUN line is unfortunately
interpreted by TCL rather than a regular shell. The llvm.exp bug has
allowed this...
2007 Nov 27
0
[LLVMdev] Problem with regression tests using stderr
...removing the associated code from llvm.exp and fixing
> the bug. This will take a while though, at it exposes a large number of
> failures that are currently hidden.
>
>> If you want to catch stderr, there is one test doing that:
>>
>> Analysis/ScalarEvolution/2007-07-15-NegativeStride.ll:
>>
>> ; RUN: llvm-as < %s | opt -analyze -scalar-evolution 2>&1 | grep
>> "Loop bb: 100 iterations"
>
> 2>&1 doesn't evoke the desired behavior; the RUN line is unfortunately
> interpreted by TCL rather than a regular shell. The llvm.e...
2007 Nov 21
0
[LLVMdev] Problem with regression tests using stderr
...ver to how things used to be done. IIRC,
you had to have the && at the end of the RUN line if you had another
RUN line that needed to be executed. That's no longer the case, of
course.
If you want to catch stderr, there is one test doing that:
Analysis/ScalarEvolution/2007-07-15-NegativeStride.ll:
; RUN: llvm-as < %s | opt -analyze -scalar-evolution 2>&1 | grep
"Loop bb: 100 iterations"
-bw
2007 Nov 27
1
[LLVMdev] Problem with regression tests using stderr
...from llvm.exp and fixing
> > the bug. This will take a while though, at it exposes a large number of
> > failures that are currently hidden.
> >
> >> If you want to catch stderr, there is one test doing that:
> >>
> >> Analysis/ScalarEvolution/2007-07-15-NegativeStride.ll:
> >>
> >> ; RUN: llvm-as < %s | opt -analyze -scalar-evolution 2>&1 | grep
> >> "Loop bb: 100 iterations"
> >
> > 2>&1 doesn't evoke the desired behavior; the RUN line is unfortunately
> > interpreted by TCL rather th...
2007 Nov 20
2
[LLVMdev] Problem with regression tests using stderr
I was attempting to write a test that involves grepping though the
stderr produced by opt -analyze, but found that my test was passing
even before I fixed the bug I was writing the test for!
I found that this one-line sure-fail test:
; RUN: echo hi |& false
passes. I also tried 2>&1, because I've seen some tests do that,
though that doesn't appear to work in this context