-
Notifications
You must be signed in to change notification settings - Fork 745
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
[threads] Add a "shared-everything" feature #6658
Conversation
src/wasm/wasm-type.cpp
Outdated
@@ -949,7 +955,9 @@ FeatureSet Type::getFeatures() const { | |||
if (sig.results.isTuple()) { | |||
feats |= FeatureSet::Multivalue; | |||
} | |||
} else if (heapType->isContinuation()) { | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can something be both a signature and a continuation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, but the original else-if up above was incorrect because it is possible for something to have a non-trivial rec group or have a declared supertype or be open and also be a signature. Rather than mix ifs and if-elses, I just made everything an if.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that part made sense to me. But maybe it's still good to have an if-else chain after it, for the disjoint cases? That seems clearer to me (even if it might lead to some overlapping code).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough.
Add the feature and flags to enable and disable it. Require the new feature to be enabled for shared heap types to validate. To make the test work, update the validator to actually check features for global types.
Add the feature and flags to enable and disable it. Require the new feature to
be enabled for shared heap types to validate. To make the test work, update the
validator to actually check features for global types.