Skip to content
#

jit

Here are 444 public repositories matching this topic...

coolreader18
coolreader18 commented Apr 21, 2021

See e.g. #2570. Some of the unit tests there with "wrong error message" should be somewhat easy to fix - just correct the error message we have to match CPython's. Others might be trickier, since you'll need to add diagnostics to recognize bad syntax and give a more detailed error than "unexpected token". Also, I think around half of them could be fixed just by adding "invalid syntax" in the messa

good first issue
marek-safar
marek-safar commented Jul 30, 2019

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

  • Culture Data
  • Any PAL related code
  • Unused icalls
fitzgen
fitzgen commented Dec 11, 2020

In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.

We can make this more efficient, improving the number of test cases we fuzz in a

good first issue fuzzing

Improve this page

Add a description, image, and links to the jit topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the jit topic, visit your repo's landing page and select "manage topics."

Learn more