Support GCC-specific __extension__ keyword #20
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
Some projects which are specifically written to be compiled by GCC use GCC-specific extensions to the C language, such as the "__extension__" keyword.
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.
Some projects which are specifically written to be compiled by GCC use GCC-specific
extensions to the C language, such as the
__extension__keyword. This is an interesting extension; it has no effect on the meaning of the code, but merely suppresses compiler warnings. Therefore, the AST does not need to change in any way.The modifications to the grammar were made after carefully examining the source for the GCC parser to see where
__extension__can be used in GNU C.