Right now the op custom assembly is a bit arbitrary; we use () and , and other keywords without a consistent scheme. For example, spv.globalVariable wraps initializer SSA value with intializer(...) but for other ops SSA values are typically just separated with comma. Another example is that spv.Load/spv.Store wraps memory operands like "Volatile" with [...] but for other ops we typically don't. We should define a consistent scheme.
Right now the op custom assembly is a bit arbitrary; we use
()
and,
and other keywords without a consistent scheme. For example, spv.globalVariable wraps initializer SSA value withintializer(...)
but for other ops SSA values are typically just separated with comma. Another example is that spv.Load/spv.Store wraps memory operands like "Volatile" with[...]
but for other ops we typically don't. We should define a consistent scheme.