Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feasibility of including pyosys #8

Closed
thasti opened this issue Jul 15, 2020 · 5 comments
Closed

Feasibility of including pyosys #8

thasti opened this issue Jul 15, 2020 · 5 comments
Labels

Comments

@thasti
Copy link

@thasti thasti commented Jul 15, 2020

Hi! This is a great project, thanks for the hard work on it!

Here's my question: I developed a couple of Python applications that use pyosys to do some synthesis/analysis work. Due to the nature of the host OS, packaging and distributing yosys to users of those tools is not a great experience at the moment. I feel like yowasp-yosys could improve that dramatically if it also allowed access to pyosys. This would also somehow fit nicely with the fact that it's being installed via a python package manager?
Being unfamiliar with wasm generally, I wonder if that's feasible at all, given pyosys depends on libyosys?

@whitequark
Copy link
Member

@whitequark whitequark commented Jul 15, 2020

It is infeasible. There's nothing I can do to allow it; the only way to get a WASM pyosys is to compile Yosys and Python to WASM together, in which case it'll work together with an isolated, ABI-incompatible version of Python embedded in the yowasp package.

@proppy
Copy link

@proppy proppy commented Dec 20, 2021

wouldn't it be possible to compile libyosys (without the pyosys part) thru the wasi-sdk toolchain and expose an API similar to pyosys?

that's a bit different from the originally feature request and would likely leverage different tooling (https://github.com/bytecodealliance/wit-bindgen instead of pywrap) but it would fully the same goal (exposing a richer python in a cross platform compatible way).

@whitequark
Copy link
Member

@whitequark whitequark commented Dec 20, 2021

Technically, yes; but the amount of work there is enormous and not something I can justify, either from the development or from the maintenance side.

@proppy
Copy link

@proppy proppy commented Dec 20, 2021

is that something that could be in theory contributed to the yowasp_yosys project? or would you rather have it maintained separately?

@whitequark
Copy link
Member

@whitequark whitequark commented Dec 20, 2021

In theory, yes, such bindings could eventually become a part of the YoWASP project. I would like to see them separate from yowasp-yosys; a distinct yowasp-libyosys repository and package seem like a good approach.

If someone would design and implement a prototype, under a different name of course, and it would match the quality of existing YoWASP projects, I would accept it under the umbrella and take up part of the maintenance, chiefly the release workflow. I would still need another maintainer to track the API changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants