GCC 2.95 support#177
Draft
Un1q32 wants to merge 1 commit into
Draft
Conversation
Contributor
Author
|
This has a fuckton of merge conflicts now but I don't wanna fix it just for it to break again in a couple days. I'll wait for #176 and then maybe try to do gcc 2.96RH so the diff can be smaller. |
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
1 participant
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.
This is ready but depends on #176 so its marked as draft until that gets merged.
Adds support for building with GCC 2.95.
GCC 2.95's C mode, even with
-std=gnu9x, doesn't support mixed declarations and code, which makes it impossible to adapt butterscotch to support it without major effort. It would basically be a full C89 conversion, and would be a monumental diff. This is unacceptable.The solution was to target GCC 2.95's C++ mode. C++ has supported mixed declarations and code for much longer, so I just made the changes required to build with
g++ -fpermissive. You must use-fpermissivebecause otherwise GCC will error whenever you implicitly cast avoid *to another pointer type.