[SR-9969] Issues in latest lldb code while building Apple Swift 5 toolchain on PowerPC64LE

[swift-ci]

Previous ID	SR-9969
Radar	None
Original Reporter	stamba (JIRA User)
Type	Bug

Environment

PowerPC64LE

Additional Detail from JIRA

| | | |------------------|-----------------| |Votes | 0 | |Component/s | LLDB for Swift | |Labels | Bug | |Assignee | None | |Priority | Medium | md5: 586d33ad9acb4edf6dd0782291944b97

Issue Description:

Following errors are seen after downloading latest Swift master branch:- – check-swift-all-optimize-linux-powerpc64le finished – — Finished tests for swift —

• mkdir -p /home/sar/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/test-results
• pushd /home/sar/swift-source/build/buildbot_linux/lldb-linux-powerpc64le ~/swift-source/build/buildbot_linux/lldb-linux-powerpc64le ~/swift-source/swift
• /home/sar/swift-source/build/buildbot_linux/ninja-build/ninja unittests/LLDBUnitTests [1/2][ 50%][2.062s] Building CXX object unittests/Utility/CMakeFiles/UtilityTests.dir/ReproducerInstrumentationTest.cpp.o FAILED: unittests/Utility/CMakeFiles/UtilityTests.dir/ReproducerInstrumentationTest.cpp.o /usr/bin/clang++ -DGTEST_HAS_RTTI=0 -DGTEST_HAS_TR1_TUPLE=0 -DGTEST_LANG_CXX11=1 -DHAVE_ROUND -DLIBXML2_DEFINED -DLLDB_CONFIGURATION_RELEASE -D_DEBUG -DSTDC_CONSTANT_MACROS -DSTDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Iunittests/Utility -I/home/sar/swift-source/lldb/unittests/Utility -Iinclude -I/home/sar/swift-source/lldb/include -I/home/sar/swift-source/llvm/include -I/home/sar/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/include -I/home/sar/swift-source/llvm/tools/clang/include -I/home/sar/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/tools/clang/include -I/home/sar/swift-source/build/buildbot_linux/swift-linux-powerpc64le/include -I/home/sar/swift-source/swift/include -I/home/sar/swift-source/lldb/source -I/usr/include/python2.7 -I/home/sar/swift-source/lldb/tools/clang/include -I../clang/include -I/usr/include/libxml2 -I/home/sar/swift-source/lldb/unittests -I/home/sar/swift-source/llvm/utils/unittest/googletest/include -I/home/sar/swift-source/llvm/utils/unittest/googlemock/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -w -fdiagnostics-color -ffunction-sections -fdata-sections -Wno-deprecated-declarations -Wno-unknown-pragmas -Wno-strict-aliasing -Wno-deprecated-register -Wno-vla-extension -O3 -UNDEBUG -include /home/sar/swift-source/lldb/unittests/gtest_common.h -fno-exceptions -fno-rtti -MMD -MT unittests/Utility/CMakeFiles/UtilityTests.dir/ReproducerInstrumentationTest.cpp.o -MF unittests/Utility/CMakeFiles/UtilityTests.dir/ReproducerInstrumentationTest.cpp.o.d -o unittests/Utility/CMakeFiles/UtilityTests.dir/ReproducerInstrumentationTest.cpp.o -c /home/sar/swift-source/lldb/unittests/Utility/ReproducerInstrumentationTest.cpp /home/sar/swift-source/lldb/unittests/Utility/ReproducerInstrumentationTest.cpp:245:18: error: default initialization of an object of const type 'const Pod' without a user-provided default constructor static const Pod p; ^ {} 1 error generated. ninja: build stopped: subcommand failed. Building the standard library for: swift-stdlib-linux-powerpc64le Running Swift tests for: check-swift-all-linux-powerpc64le check-swift-all-optimize-linux-powerpc64le ./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting ./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting

[belkadan]

This seems like it'd be platform-independent, so there must be something funny going on. What does the Pod type look like?