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

Tracer is issuing excessive amounts of stat() syscalls #170

Closed
whitequark opened this issue Aug 8, 2019 · 2 comments
Closed

Tracer is issuing excessive amounts of stat() syscalls #170

whitequark opened this issue Aug 8, 2019 · 2 comments
Labels
bug
Milestone
0.1

Comments

@whitequark
Copy link
Contributor

For unknown reasons, the strace of any nMigen synthesis run looks like this:

stat("/home/whitequark/Projects/nmigen/nmigen/tracer.py", {st_mode=S_IFREG|0644, st_size=1883, ...}) = 0
stat("/home/whitequark/Projects/nmigen/nmigen/hdl/ast.py", {st_mode=S_IFREG|0644, st_size=47434, ...}) = 0
stat("/home/whitequark/Projects/nmigen/nmigen/hdl/xfrm.py", {st_mode=S_IFREG|0644, st_size=22180, ...}) = 0

And this goes on for several tens of thousands of lines. This is likely why nMigen elaboration is so much slower than oMigen's.
@whitequark whitequark added the bug label Aug 8, 2019
@whitequark
Copy link
Contributor Author

cc @programmerjake --you mentioned that nMigen elaboration is very slow, and is even slower on PyPy; this seems to be why.

@whitequark
Copy link
Contributor Author

Fixed in 4ee82c9.

@whitequark whitequark added this to the 0.1 milestone Aug 22, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
1 participant
@whitequark