Issue metadata
Sign in to add a comment
|
v8 compilation failures on ChromeOS release builds |
||||||||||||||||||||||||
Issue descriptionFive builders failed. For instance this one: https://uberchromegw.corp.google.com/i/chromeos/builders/kevin-release/builds/691 https://uberchromegw.corp.google.com/i/chromeos/builders/kevin-release/builds/691/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio chromeos-chrome-57.0.2956.0_rc-r1: [11/10825] CXX v8_snapshot/obj/v8/v8_base/assembler-arm.o chromeos-chrome-57.0.2956.0_rc-r1: FAILED: v8_snapshot/obj/v8/v8_base/assembler-arm.o chromeos-chrome-57.0.2956.0_rc-r1: x86_64-pc-linux-gnu-g++ -MMD -MF v8_snapshot/obj/v8/v8_base/assembler-arm.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DGOOGLE_CHROME_BUILD -DENABLE_MEDIA_ROUTER=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DV8_I18N_SUPPORT -DENABLE_HANDLE_ZAPPING -DV8_USE_EXTERNAL_STARTUP_DATA -DV8_TARGET_ARCH_ARM -DCAN_USE_ARMV7_INSTRUCTIONS -DUSE_EABI_HARDFLOAT=1 -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -I../../../../../../../home/chrome-bot/chrome_root/src -Iv8_snapshot/gen -I../../../../../../../home/chrome-bot/chrome_root/src/v8 -I../../../../../../../home/chrome-bot/chrome_root/src/v8/include -I../../../../../../../home/chrome-bot/chrome_root/src/third_party/icu/source/common -I../../../../../../../home/chrome-bot/chrome_root/src/third_party/icu/source/i18n -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pipe -m32 -msse2 -mfpmath=sse -mmmx -pthread -g2 -gsplit-dwarf -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -O3 -fno-ident -fdata-sections -ffunction-sections -fno-threadsafe-statics -fvisibility-inlines-hidden -std=gnu++11 -fno-rtti -fno-exceptions -Wno-deprecated -Wno-narrowing -c ../../../../../../../home/chrome-bot/chrome_root/src/v8/src/arm/assembler-arm.cc -o v8_snapshot/obj/v8/v8_base/assembler-arm.o chromeos-chrome-57.0.2956.0_rc-r1: ../../../../../../../home/chrome-bot/chrome_root/src/v8/src/arm/assembler-arm.cc:173:2: error: #error "CAN_USE_ARMV7_INSTRUCTIONS should match CAN_USE_VFP3_INSTRUCTIONS" chromeos-chrome-57.0.2956.0_rc-r1: #error "CAN_USE_ARMV7_INSTRUCTIONS should match CAN_USE_VFP3_INSTRUCTIONS" chromeos-chrome-57.0.2956.0_rc-r1: ^ also gru, elm, oak and kip failed in BuildPackages (probably with the same error)
,
Dec 20 2016
https://uberchromegw.corp.google.com/i/chromeos/builders/kip-release/builds/761/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio kip-release is a different issue (timeout), all the other boards are armv8, see duplicated bug. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by diand...@chromium.org
, Dec 20 2016Status: Duplicate (was: Untriaged)