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.

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

Investigating CompositeExplicitAugograd dispatch key #982

Open
xytintel opened this issue Oct 18, 2024 · 1 comment
Open

Investigating CompositeExplicitAugograd dispatch key #982

xytintel opened this issue Oct 18, 2024 · 1 comment
Labels

Comments

@xytintel
Copy link
Contributor

🚀 The feature, motivation and pitch

Whether CompositeExplicitAugograd codegen flag is needed requires further investigation.

image

Alternatives

No response

Additional context

No response

@xytintel
Copy link
Contributor Author

  • CompositeExplicitAutograd (previously known as DefaultBackend):
    implementations of kernels that work for all backends, but require an
    explicit definition of backward function in derivatives.yaml to support autograd.
    The most typical use of this key are for delegating functions; i.e.,
    functions that do a very small amount of work and then delegate to another
    operator to do the actual heavy lifting. Under the hood, registering a
    kernel to CompositeExplicitAutograd is equivalent to registering that
    kernel to every backend (e.g., CPU, CUDA). Note: kernels which call
    DispatchStub should NOT be registered as CompositeExplicitAutograd, as
    DispatchStub only works for CPU, CUDA)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant