-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
A-target-specsArea: Compile-target specificationsArea: Compile-target specificationsA-targetsArea: Concerning the implications of different compiler targetsArea: Concerning the implications of different compiler targetsO-wasiOperating system: Wasi, Webassembly System InterfaceOperating system: Wasi, Webassembly System InterfaceT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
WASI supports different features depending on whether it is p1 or p2. Additionally, p1-threads support threads. The problem is that we cannot determine these distinctions using cfg or similar mechanisms. In crates like tokio, it's impossible to create conditional compilation branches with cfg, such as 'this feature is not available in p1 but is supported in p2, so let's create a conditional branch.'
Therefore, I would like to request support for a method to distinguish WASI targets more precisely using cfg or a similar mechanism.
Metadata
Metadata
Assignees
Labels
A-target-specsArea: Compile-target specificationsArea: Compile-target specificationsA-targetsArea: Concerning the implications of different compiler targetsArea: Concerning the implications of different compiler targetsO-wasiOperating system: Wasi, Webassembly System InterfaceOperating system: Wasi, Webassembly System InterfaceT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.