In the Fedora Linux distribution package for abseil-cpp, we find that Symbolize.SymbolizeWithMultipleMaps in absl_symbolize_test fails on the s390x architecture. When the test fails, a message like
/builddir/build/BUILD/abseil-cpp-20210324.2/absl/debugging/symbolize_test.cc:315: Failure
Expected equality of these values:
"kPadding1"
buf
Which is: ""
/builddir/build/BUILD/abseil-cpp-20210324.2/absl/debugging/symbolize_test.cc:349: Failure
Expected equality of these values:
expected[i]
Which is: "kPadding1"
buf
Which is: ""
/builddir/build/BUILD/abseil-cpp-20210324.2/absl/debugging/symbolize_test.cc:349: Failure
Expected equality of these values:
expected[i]
Which is: "kPadding1"
buf
Which is: ""
is printed.
When LTO is disabled in the build, the test does not fail.
Steps to reproduce the bug
The error can be observed in the RPM build infrastructure for Fedora Linux, but there is nothing particularly special about how we are building the library, and there are no significant downstream patches involved. I expect that this error can probably be reproduced on any s390x system when combined with LTO.
While I don’t have convenient interactive access to real s390x hardware, I can easily test patches or try experiments on real hardware by submitting “scratch” RPM builds.
Describe the bug
In the Fedora Linux distribution package for
abseil-cpp
, we find thatSymbolize.SymbolizeWithMultipleMaps
inabsl_symbolize_test
fails on thes390x
architecture. When the test fails, a message likeis printed.
When LTO is disabled in the build, the test does not fail.
Steps to reproduce the bug
The error can be observed in the RPM build infrastructure for Fedora Linux, but there is nothing particularly special about how we are building the library, and there are no significant downstream patches involved. I expect that this error can probably be reproduced on any
s390x
system when combined with LTO.What version of Abseil are you using?
20111102.0
What operating system and version are you using
Fedora Linux Rawhide/37 (development version)
What compiler and version are you using?
What build system are you using?
Additional context
We are using https://github.com/abseil/abseil-cpp/archive/20111102.0/abseil-cpp-20111102.0.tar.gz with:
ninja
backend)gtest
/gmock
1.11.0While I don’t have convenient interactive access to real
s390x
hardware, I can easily test patches or try experiments on real hardware by submitting “scratch” RPM builds.I have attached a complete failing build log including compiler flags.
No other architectures (of
x86_64
,i686
,aarch64
, andppc64le
) are affected.