This change makes it so that passing --shared-memory is all a user
needs to do to get proper multithreaded code. This default can still
be explicitly overridden for any reason using --passive-segments and
--active-segments.
Details
Details
- Reviewers
sbc100 quantum - Commits
- rGf04c5c0d1a38: Merging r366504: --------------------------------------------------------------…
rL366709: Merging r366504:
rG6a6f28f7b720: [WebAssembly] Use passive segments by default when memory is shared
rL366504: [WebAssembly] Use passive segments by default when memory is shared
rLLD366504: [WebAssembly] Use passive segments by default when memory is shared
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 35311 Build 35310: arc lint + arc unit
Event Timeline
lld/wasm/Driver.cpp | ||
---|---|---|
323–325 | This logic seems a bit hard to understand... Would this work? args.hasFlag(OPT_passive_segments, OPT_active_segments, config->sharedMemory); |
Comment Actions
- Simplify flags logic
lld/wasm/Driver.cpp | ||
---|---|---|
323–325 | Nice! I thought that bool was for something else entirely. |
This logic seems a bit hard to understand...
Would this work?