[LLVMdev] piping into lli broken on darwin

Tobias Grosser
2012-11-01T06:34:20Z

On 10/31/2012 05:33 PM, Eli Friedman wrote:
> On Wed, Oct 31, 2012 at 5:26 PM, Jack Howarth <howarth at
bromo.med.uc.edu> wrote:
>> On Wed, Oct 31, 2012 at 05:17:28PM -0700, Eli Friedman wrote:
>>> On Wed, Oct 31, 2012 at 5:01 PM, Jack Howarth <howarth at
bromo.med.uc.edu> wrote:
>>>> On Wed, Oct 31, 2012 at 04:43:42PM -0700, Eli Friedman wrote:
>>>>> On Wed, Oct 31, 2012 at 4:33 PM, Jack Howarth <howarth
at bromo.med.uc.edu> wrote:
>>>>>> On Wed, Oct 31, 2012 at 03:53:50PM -0700, Eli Friedman
wrote:
>>>>>>> On Wed, Oct 31, 2012 at 8:43 AM, Jack Howarth
<howarth at bromo.med.uc.edu> wrote:
>>>>>>>>    While testing llvm/polly svn on
x86_64-apple-darwin10/11/12, I noticed that three darwin
>>>>>>>> specific polly-test regressions exist. At least
part of these failures appear to be due
>>>>>>>> to lli on darwin not accepting piped input such
that the test...
>>
>>    Expected Passes    : 125
>>    Expected Failures  : 29
>>    Unsupported Tests  : 2
>>    Unexpected Failures: 3
>>
>> How is this issue handled in the main llvm testsuite?
>
> Ignoring the JIT tests, which are carefully written to be
> platform-independent, the regression tests in llvm/test/ generally
> don't run anything; our runtime tests mostly consist of C and C++
> code.

True. And I believe Polly should go the same road. Let's keep execution
test to the LLVM test-suite. Introducing them was OK when we where not
able to compile the llvm test-suite. Nowadays, we should just remove them.

Cheers
Tobi