Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parser: implement stdckdint.h #624

Merged
merged 1 commit into from
Feb 13, 2024
Merged

Parser: implement stdckdint.h #624

merged 1 commit into from
Feb 13, 2024

Conversation

ehaas
Copy link
Collaborator

@ehaas ehaas commented Feb 10, 2024

Closes #578

@ehaas
Copy link
Collaborator Author

ehaas commented Feb 10, 2024

Should we move CallExpr into its own file (mostly to hold the custom-typechecking code for special builtins)?

Copy link
Owner

@Vexu Vexu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Should we move CallExpr into its own file (mostly to hold the custom-typechecking code for special builtins)?

It would be nice to keep Parser.zig from getting too big if you can extract it cleanly.

@@ -4794,7 +4794,11 @@ const CallExpr = union(enum) {
Builtin.tagFromName("__va_start").?,
Builtin.tagFromName("va_start").?,
=> arg_idx != 1,
Builtin.tagFromName("__builtin_complex").? => false,
Builtin.tagFromName("__builtin_complex").?,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we sure these are memoized properly? Getting a bit worried about something like ziglang/zig#7948 happening here

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how to know if that's happening - I had to up the eval branch quote for checkVarArg - is that why you ask?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is that why you ask?

No just because there are so many calls now. I checked with @compileLog and they are getting memoized properly.

@ehaas ehaas merged commit 53907e5 into Vexu:master Feb 13, 2024
3 checks passed
@ehaas ehaas deleted the stdckdint branch February 18, 2024 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

C23 support: Add stdckdint.h
2 participants