Page MenuHomePhabricator

[WebAssembly] Allow multivalue signatures in object files

Authored by tlively on Oct 17 2019, 9:22 PM.



Also changes the wasm YAML format to reflect the possibility of having
multiple return types and to put the returns after the params for
consistency with the binary encoding.

Diff Detail

Event Timeline

tlively created this revision.Oct 17 2019, 9:22 PM
aheejin accepted this revision.Oct 18 2019, 5:22 AM
aheejin added inline comments.

Unrelated question to this CL: Do we treat pair and packed pair in the same way?

This revision is now accepted and ready to land.Oct 18 2019, 5:22 AM
sbc100 accepted this revision.Oct 18 2019, 10:26 AM



Do we want to error out somehow if the feature flags of the object file don't include multi-value?

tlively marked 2 inline comments as done.Oct 18 2019, 10:48 AM
tlively added inline comments.

That's an interesting idea! I don't think we have a precedent for that kind of validation in the object file parser. It would also be somewhat intrusive, since the target features section is one of the last sections to be parsed, so there would have to be a separate step at the end where feature invariants are checked. The invariants we could check in such a step would also be limited since individual instructions are not exposed in the object file abstraction.


Hmm, I guess this isn't a great test because there wouldn't be any padding in this struct anyway, so in this case it literally is the same. I'm not sure what would happen with a packed struct that should contain padding. I'll add a better test in a follow up CL.

This revision was automatically updated to reflect the committed changes.