Move SingleFunctionCompiler into its own crate, cranelift-simplecompiler

[abrown]

While experimenting with using this together with cranelift-interpreter, I realized that having SingleFunctionCompiler in cranelift-filetests creates a circular dependency. Moving this functionality out to its own crate breaks that cycle. I am quite open to other approaches (merge together with simplejit somehow?) or crate name suggestions.

[github-actions]

Subscribe to Label Action

cc @bnjbvr

Details

This issue or pull request has been labeled: "cranelift"

Thus the following users have been cc'd because of the following labels:

• bnjbvr: cranelift

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

[abrown]

cc: @alexcrichton, @yurydelendik: I saw that you were moving stuff around in wasmtime-jit in #1761 and wondered if you had any better ideas of where to put this SingleFunctionCompiler... it probably needs to stay in Cranelift-land but I'm checking just in case there is a better place it should go.

[alexcrichton]

Ah I think #1761 is largely just juggling wasmtime data structures and the code produced by cranelift, so I don't think it's too too connected to this. As for how this is organized, I don't have too many opinions myself!

[abrown]

Too old!