Hi!

I am using the wasm2js tool on a WebAssembly module written in Rust using wasm-bindgen(no emscripten involved) to generate code that works on Internet Explorer. However, since I added a new library which internally makes use of i64, this import has been added to the wasm2js output:

import { getTempRet0 } from 'env';

From what I understand, this method is used by

Present license file does not look right. Need to change it to the correct one

Big thanks for making this cool tool open-source.

By any chance, is there a complete list of instructions which are currently not supported / under development please? For instance, I am aware that vgatherdpd does not work.

Author Name: Wilson Snyder (@wsnyder)
Original Redmine Issue: 1639 from https://www.veripool.org

Good starter task is to implement and test $countbits, which is a generation of $countones etc.

The existing $countones functions inside V3Number could be removed to use the new generic countbits. The runtime functions in verilated.h should remain specialized, as that will help pe

00_index.ipynb

• Broken link to operator class in first para

01_data_regions.ipynb

• Where to find descriptions of operator options like dle='noop'
• Could the generated code have a comment at the top of the structs to define what the members are (size, npsize, dsize, hsize, hofs, oofs). Yeah, I know it isn't really for human reading ... I suppose I would see those use

Description

Unable to receive a prompt for SSH Private Key passphrase

Actual behavior

When adding a private key to the configs, I get failures due to missing passphrase

Expected behavior

I expect a prompt asking me for my passphrase, as with the username/password auth.

Steps to reproduce

Add an encrypted private key to the config but do not add the passphrase.

The current runtime source generates a lot of warnings when being compiled. We should go through and fix the ones we can and suppress the ones we think are OK.

This is kind of like #27, but I don' think people who are just starting out should worry about how to set up a package to go into opam.

What I have in mind is a guide that tells you how to release a package in simple cases, but notes likely potential gotchas, and has links to further info for more complex cases and for understaning the process under the hood.

This is something I'm trying to