BEP requires -ffile-prefix-map which is available in GCC 8 onwards

[feng-jianwei]

assert/include/boost/assert/source_location.hpp

Line 180 in 425b5ba

# define BOOST_CURRENT_LOCATION ::boost::source_location(__builtin_FILE(), __builtin_LINE(), __builtin_FUNCTION())

Although __builtin_FILE () is available in gcc7, -ffile-prefix-map is not supported in gcc7. When the gcc7 version is used in a project, there will be bep consistency problems. It is recommended to increase the version number in the macro.
patch：
-#elif defined(BOOST_GCC) && BOOST_GCC >= 70000
+#elif defined(BOOST_GCC) && BOOST_GCC >= 80000

-// The built-ins are available in 4.8+, but are not constant expressions until 7
+// The built-ins are available in 4.8+, but BEP requires -ffile-prefix-map which is available in GCC 8 onwards

[pdimov]

I don't understand how this helps. If __builtin_FILE() is not used, __FILE__ will be used instead, and it won't be affected by the nonexistent -ffile-prefix-path either.

[feng-jianwei]

I don't understand how this helps. If __builtin_FILE() is not used, __FILE__ will be used instead, and it won't be affected by the nonexistent -ffile-prefix-path either.

Although __FILE__ can also cause binary differences, the differences caused by __FILE__ can be resolved. The difference is that __builtin_FILE()is a built-in function, whereas __FILE__ is a macro definition. We can resolve it by using -D__FILE__.

[pdimov]

What does the BEP abbreviation stand for?

[feng-jianwei]

What does the BEP abbreviation stand for?

BEP=Binary Equivalence Project
Based on the same source code and the same environment, the same version can be reproducibly built, and the build results are completely consistent.
it aims to ensure that the software's build process from source code to binary code is consistent and verifiable.
You can find the Build Path tab in the https://reproducible-builds.org/docs/env-variations/ to learn more about this.