-
Notifications
You must be signed in to change notification settings - Fork 242
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
Design of Invokers #216
Comments
On FP16_ALT support in InvokersFP16_ALT requires support for selection of "FP16 mode" during kernel invocation. The necessary parameter is passed to the Invoker and it is the Invoker who must properly handle it. How it should be done is a design choice:
|
On usage of member functions in InvokersOnly static member functions are allowed to use from within the Invoker (or you must instantiate the class first). The simplest is to use the normal function instead. More info at #1971. |
[Attribution] @junliume @johnny-keker Please set https://github.com/ROCmSoftwarePlatform/MIOpen/labels/specification and remove https://github.com/ROCmSoftwarePlatform/MIOpen/labels/request_for_comments Please also assign @iq136boy @illsilin @JehandadKhan |
Pitfall with capturing slicesCapturing values in Invoker/Factory labdas: be careful when using |
The internals of our library went some major changes recently with solver registry, invokers etc. It would be helpful to have a design document to understand what the new design looks like.
Motivation and basic concepts
See Extend Solver/Solution architecture with Invoker objects. #1127
Design of Invokers
Initial design is explained in the description of PR #2192, Invokers core and Forward Direct
Further reading (more code than text 👀)
slice
and similar things, see note in PR #800.Please do not hesitate to ask specific questions.
The text was updated successfully, but these errors were encountered: