fix: Recognize __uint128_t in the C lexer and parser.#1
Merged
Conversation
The signed __int128_t was already handled, but the unsigned __uint128_t keyword was missing, so buildlib failed to parse system headers that use it (e.g. aarch64-linux-musl bits/signal.h). The uint128_type it maps to already exists in absyn.
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 signed
__int128_twas already handled, but the unsigned__uint128_tkeyword was missing, sobuildlibfailed to parse system headers that use it (e.g.aarch64-linux-muslbits/signal.h, used transitively viaaio.h).The
uint128_typeit maps to already exists in absyn — only the lexer keyword and the grammar token + rule were missing.This unblocks cross-compiling the Cyclone libc bindings for arm64.
This change is