Remove support and downstream testing for GCC 10#50
Merged
pearzt merged 1 commit intotudasc:develfrom Jul 10, 2025
Merged
Conversation
sebastiankreutzer
approved these changes
Jul 10, 2025
This file contains hidden or 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
3 participants
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 is around 5 years old by now and, as far as we're currently aware, not a default compiler for any major distribution. Currently, we still test MetaCG using GCC 10 in our downstream CI, but the build are currently failing due a template resolution problem in pymetacg. As briefly discussed during one of our past meetings, I propose to drop support for GCC 10, but would be open to expanding the range of GCC versions again when we move the CI to the new module system on Lichtenberg.