Skip to content
#

runtime

Here are 845 public repositories matching this topic...

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

Thihup
Thihup commented Aug 19, 2021

Current, if we try to run a more recent Java class in an old JVM, we get the following error message:

Error: LinkageError occurred while loading main class some.Class
	java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=some/Class, offset=6

However, it is not so easily to detect that the class was compiled with a version above the supported by the JVM.Hotspot

bkolobara
bkolobara commented Dec 14, 2021

Currently, if you create an environment from a process that has the permission to call lunatic::process::allow_namespace it can give greater permissions to sub-processes spawned into the new environment than it has itself.

The lunatic::process::allow_namespace host function should first check if we have permissions for the namespace before allowing us to add it to other environments. Simila

Improve this page

Add a description, image, and links to the runtime 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 runtime topic, visit your repo's landing page and select "manage topics."

Learn more