Skip to content

[threads] Parse, build, and print shared composite types #6654

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

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

tlively
Copy link
Member

@tlively tlively commented Jun 12, 2024

Parse the text format for shared composite types as described in the shared-everything thread proposal. Update the parser to use 'comptype' instead of 'strtype' to match the final GC spec and add the new syntactic class 'sharecomptype'.

Update the type canonicalization logic to take sharedness into account to avoid merging shared and unshared types. Make the same change in the TypeMerging pass. Ensure that shared and unshared types cannot be in a subtype relationship with each other.

Follow-up PRs will add shared abstract heap types, binary parsing and emitting for shared types, and fuzzer support for shared types.

Parse the text format for shared composite types as described in the
shared-everything thread proposal. Update the parser to use 'comptype' instead
of 'strtype' to match the final GC spec and add the new syntactic class
'sharecomptype'.

Update the type canonicalization logic to take sharedness into account to avoid
merging shared and unshared types. Make the same change in the TypeMerging pass.
Ensure that shared and unshared types cannot be in a subtype relationship with
each other.

Follow-up PRs will add shared abstract heap types, binary parsing and emitting
for shared types, and fuzzer support for shared types.
@tlively tlively requested a review from kripken June 12, 2024 01:12
Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

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

Is SET "shared everything threads"?

@tlively
Copy link
Member Author

tlively commented Jun 12, 2024

Yes, other options include [shared] or [threads]. Do you have a preference?

@kripken
Copy link
Member

kripken commented Jun 12, 2024

Hmm, SET took me a while to get, so maybe one of those others. Or [shared-everything]? That might be a little long though. I'm ok either way.

@tlively
Copy link
Member Author

tlively commented Jun 12, 2024

I'll go with [threads].

@tlively tlively merged commit 0e11876 into main Jun 12, 2024
@tlively tlively deleted the set-shared-comptype branch June 12, 2024 19:30
@tlively tlively changed the title [SET] Parse, build, and print shared composite types [threads] Parse, build, and print shared composite types Jun 13, 2024
@gkdn gkdn mentioned this pull request Aug 31, 2024
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.

2 participants