You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Command queue - effectively maps to etrt streams, but there may be lifetime issues and we can run one kernel at a time, probably should start with synchronous implementation.
Q. Where do we put all the build requirements, like linker.ld?
Q. Do we include unsupported instruction checker? As part of tests?
Renderer. The most difficult part. ET runs kernels written in C, but there are enough architectural peculiarities to make it pretty complicated - it's neither "CPU backend", nor very GPU like (pretty close though).
Based on project architecture, ET related changes will likely touch multiple places of the code tree, including some "generic" modules - optimizer, beam search, etc. tinygrad is very fast moving project, so our goal should be to upstream ET related changes as soon as possible and until then - keep et branch in sync with upstream. This may prove a challenge.
Obviously, all tinygrad development guidelines apply.
Activity