strange build failure with llvm

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

strange build failure with llvm

patrick keshishian
Hello,

I'm just curious if this type of failures have been seen by those
doing bulk builds?

The full log file is about 4MB. I don't mind sharing, but it is
uninteresting except for these lines (let me know if you want it).

System is  Supermicro X7SPA-HF (atom) processor
Running cvs updated OPENBSD_6_0 on 2016/09/27 (dmesg sent to dmesg@)


Using dpb(1) to build some package when llvm failed like so:


[1413/2511] cd /usr/build/ports/pobj/llvm-3.8.0/build-amd64/lib/Target/Mips
&& /usr/build/ports/pobj/llvm-3.8.0/build-amd64/bin/llvm-tblgen
-gen-asm-matcher -I
/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips -I
/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target -I
/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/include
/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips/Mips.td
-o /usr/build/ports/pobj/llvm-3.8.0/build-amd64/lib/Target/Mips/MipsGenAsmMatcher.inc.tmp
[1414/2511] cd /usr/build/ports/pobj/llvm-3.8.0/build-amd64/lib/Target/Mips
&& /usr/local/bin/cmake -E copy_if_different
/usr/build/ports/pobj/llvm-3.8.0/build-amd64/lib/Target/Mips/MipsGenAsmMatcher.inc.tmp
/usr/build/ports/pobj/llvm-3.8.0/build-amd64/lib/Target/Mips/MipsGenAsmMatcher.inc
[...]
[1870/2511] /usr/build/ports/pobj/llvm-3.8.0/bin/c++
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-Ilib/Target/Mips/AsmParser
-I/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips/AsmParser
-I/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips
-Ilib/Target/Mips -Iinclude
-I/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/include -O2 -pipe
-fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter
-Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic
-Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor
-Wno-comment -std=c++11 -ffunction-sections -fdata-sections -DNDEBUG
 -fno-exceptions -MMD -MT
lib/Target/Mips/AsmParser/CMakeFiles/LLVMMipsAsmParser.dir/MipsAsmParser.cpp.o
-MF lib/Target/Mips/AsmParser/CMakeFiles/LLVMMipsAsmParser.dir/MipsAsmParser.cpp.o.d
-o lib/Target/Mips/AsmParser/CMakeFiles/LLVMMipsAsmParser.dir/MipsAsmParser.cpp.o
-c /usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips/AsmParser/MipsAsmParser.cpp
FAILED: lib/Target/Mips/AsmParser/CMakeFiles/LLVMMipsAsmParser.dir/MipsAsmParser.cpp.o
/usr/build/ports/pobj/llvm-3.8.0/bin/c++   -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-Ilib/Target/Mips/AsmParser
-I/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips/AsmParser
-I/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips
-Ilib/Target/Mips -Iinclude
-I/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/include -O2 -pipe
-fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter
-Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic
-Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor
-Wno-comment -std=c++11 -ffunction-sections -fdata-sections -DNDEBUG
 -fno-exceptions -MMD -MT
lib/Target/Mips/AsmParser/CMakeFiles/LLVMMipsAsmParser.dir/MipsAsmParser.cpp.o
-MF lib/Target/Mips/AsmParser/CMakeFiles/LLVMMipsAsmParser.dir/MipsAsmParser.cpp.o.d
-o lib/Target/Mips/AsmParser/CMakeFiles/LLVMMipsAsmParser.dir/MipsAsmParser.cpp.o
-c /usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips/AsmParser/MipsAsmParser.cpp
In file included from
/usr/build/ports/pobj/llvm-3.8.0/llvm-3.8.0.src/lib/Target/Mips/AsmParser/MipsAsmParser.cpp:6204:0:
lib/Target/Mips/MipsGenAsmMatcher.inc: In function 'unsigned int
validateOperandClass(llvm::MCParsedAsmOperand&,
{anonymous}::MatchClassKind)':
lib/Target/Mips/MipsGenAsmMatcher.inc:2526:47: error: 'bbeak' was not
declared in this scope
     case Mips::W4: OpKind = MCK_MSA128WEvens; bbeak;
                                               ^


Observations:
1. MipsGenAsmMatcher.inc seems to be a generated file.
2. obviously "bbeak" is supposed to be "break"
3. interesting b=0x62 and r=0x72 one bit-flip difference.

Cosmic rays?

Restarting the build completed successfully.

--patrick

Reply | Threaded
Open this post in threaded view
|

Re: strange build failure with llvm

Christian Weisgerber
On 2016-09-30, patrick keshishian <[hidden email]> wrote:

> I'm just curious if this type of failures have been seen by those
> doing bulk builds?

Nope (amd64).

--
Christian "naddy" Weisgerber                          [hidden email]