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.

Sign up for GitHub

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

Jump to bottom

Figure out if pypy3 is really needed for nextpnr-xilinx repo #90

Open
mithro opened this issue Apr 23, 2020 · 3 comments
Open

Figure out if pypy3 is really needed for nextpnr-xilinx repo #90

mithro opened this issue Apr 23, 2020 · 3 comments

Comments

@mithro
Copy link
Member

mithro commented Apr 23, 2020

The dependency on pypy3.6 worries me a little. Let's merge and log an issue to follow up on that.

Originally posted by @mithro in #89
@mithro
Copy link
Member Author

mithro commented Apr 23, 2020

FYI - @acomodi

@acomodi
Copy link

acomodi commented Apr 23, 2020 •
edited
Loading

I think it might work without pypy, but it would require much more time to compile the data files (nextpnr instructions). Also cpython should be an option.

@daveshah1
Copy link
Member

PyPy3 is not needed but there was a very significant difference in database build runtime (something like 5x iirc) so it is strongly recommended. I have a speedup planned in the future that will make it less needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mithro @daveshah1 @acomodi