-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[CC] Ship the C backend! #1644
Comments
I just attempted the instructions here but I'm getting an error:
Am I doing something wrong? |
Sorry, the C backend is not release yet. You need to clone the Taichi repo and build it from source, see dev_install.rst. cmake -Bbuild -S. -DTI_WITH_CC:BOOL=ON
make -Cbuild -j4 |
Ah, got it! I'll try building from source! |
This flag enables the CC backend. See taichi-dev#1644 (comment).
Awesome, so I now got TI_ARCH=cc working by editing the Dockerfile: #1680. Now I'm faced with a new issue:
Does the CC backend not support gradients? |
Yes, that example probably needs |
Ah ok, I really need the AD system, so I'll try using taichi through PyCall.jl then for the time being. |
This flag enables the CC backend. See #1644 (comment).
Continue our talk in #1332.
Concisely describe the proposed feature
Currently our C backend is capable of passing all the tests on my end. I think it's time to officially release the C backend!
Describe the solution you'd like (if any)
CompileConfig
to modify compiler command for customizing compilers & flags ([cc] Add ti.cfg.cc_compile_cmd and ti.cfg.cc_link_cmd #1645, @archibate)Additional comments
To make C backend work on Windows could be challenging because:
%PATH%
does not have an official/bin
directory, it would be hard to seek for the correct compiler./
as option prefix instead of-
, e.g.:/O3
instead of-O3.
drand48()
could be unavailable there.So we'd release C backend on Linux and OS X first, then deal with Windows.
The text was updated successfully, but these errors were encountered: