[wasm] Add a new supported signature for pinvokes

[BrzVlad]

Ideally we would want to compute this set of signatures at compile time.

Fixes#61156

[ghost]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Ideally we would want to compute this set of signatures at compile time.

Fixes #61156

Author:	BrzVlad
Assignees:	-
Labels:	arch-wasm
Milestone:	-

[lewing]

Ideally we would want to compute this set of signatures at compile time.

Yeah this is on my list. I'll open an issue to make it clear.

[SamMonoRT]

cc @lewing - the issue is marked with 6.0.x milestone.

[TheSpydog]

Since filing the original issue (#61156) I've discovered several more unsupported pinvoke signatures in our codebase. I generated the other signatures required for our assembly with wasm-tuner, so should I submit them as a separate PR? Or should I hold off on that in favor of the upcoming change to create the signature set at compile time?

[BrzVlad]

@TheSpydog I think we should include them as part of this PR. Could you please share the cookies/hashes for these signatures ?

[TheSpydog]

Sure, the additional missing signature hashes are as follows:

IIFFFF
IIIIIDII
IIIIIFIII
LIIII

[lewing]

/azp run runtime-manual

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).