-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Enable custom-ops for tensorflow-cpu #990
Comments
Custom ops should be separated to cpu shared files and gpu shared files. |
Given the dlopen() dynamic kernel strategy that TF uses this shouldn't be required: However, I agree that your suggestion is a possible solution if for some reason we're unable this fixed. |
The problem is -
Exports of
After a simple modification of https://github.com/tensorflow/addons/blob/master/tensorflow_addons/tensorflow_addons.bzl
now returns nothing and Looks great but I've not tested how it works yet. 😆 |
Awesome, @failure-to-thrive you are the expert on magical bugs. 😂 |
Hi, I'm running into the same issue: I'm trying to use Tensorflow cpu to reduce my docker file weight and now the import yields the same error:
My only usage of Addons is for AdamW during training and the gelu activation. I know gelu has been moved to TF core: i'll try to use the nightly version and stop using the custom ops from addons. Thanks, |
Building the addons from sources fixed it for me on TF 2.2 (installed with pip). |
TensorFlow Addons is transitioning to a minimal maintenance and release mode. New features will not be added to this repository. For more information, please see our public messaging on this decision: Please consider sending feature requests / contributions to other repositories in the TF community with a similar charters to TFA: |
Currently tensorflow-cpu will fail when trying to load custom ops for
undefined symbol: __cudaPushCallConfiguration
:I'm not quite sure what is causing this without having done a deep dive, but linking this possibly related PR since this was a departure from standard TF linking:
#539
The text was updated successfully, but these errors were encountered: