Closed Baltoli closed 7 years ago
First error is: llvm-lit33: error: no such option: --xunit-xml-output
Setting the option EXPORT_XUNIT_XML=False
resolves the issue where llvm-lit33
doesn't know the xunit-xml
CLI flag.
Lots of problems with {
in function bodies - looks like some kind of version incompatibility?
The problem here seems to be that some tests have clang
rather than %clang
in their run scripts, which means that when they are compiled, the textual bitcode format is different to what tesla
scripts expect (as they are based on 3.3 while clang
is 3.8 on my machine).
Confirmed that this does fix at least one of the problem tests (integration/threading.c
). Will attempt to fix the others that exhibit this behaviour.
I think there might actually be a regression in the parsing of expressions: the test for Parsing/field-argument.c
fails. The expected region of code looks something like:
field {
type: "object"
base {
type: Variable
name: "o"
}
name: "field"
index: 0
}
but instead we have:
field {
type: "object"
base {
type: Variable
name: "field"
}
name: "field"
index: 0
}
This seems to suggest that the parser is mis-assigning the name of the base
message.
It would be nice to be able to run the TESLA test suite, so it's probably worth a bit of time looking into why I can't run them on my build.