Conversation
This enables some simplifications in target-independent files.
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.
The 32-bit x86 port of CompCert is no longer useful, now that all x86 processors made in the last 15 years are 64-bit processors and all x86 OS are 64-bit by default and increasingly stop supporting 32-bit applications. There are a few legacy embedded systems built around 32-bit x86 processors, but they lack SSE2 support, which CompCert requires to implement FP arithmetic.
At the same time, 32-bit x86 support required unnatural changes in CompCert, to accommodate peculiarities of the x86-32 ABI: FP function results returned on the FP stack, reduced alignment for
doubleandlong long, etc. Removing this code will make CompCert easier to support in the future.