Workaround GCC 10&11 optimiser compilation failure #402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GCC 10 and 11 seem to have an issue compiling the
std::lexicographical_comparestatements injson_ops.h. The issue seems to be that the operators used insidestd::lexicographical_comparearen't defined before the call tostd::lexicographical_compare.This only seems to cause a problem for GCC 10 and 11, with c++20 and optimisations enabled. Clang always rejects the code.
A reduced example of the problem: https://godbolt.org/z/9ra6hn7c9