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

Categorical HM integration with Spatial kernel implementations #309

Open
mattfel1 opened this issue Jun 15, 2020 · 2 comments
Open

Categorical HM integration with Spatial kernel implementations #309

mattfel1 opened this issue Jun 15, 2020 · 2 comments

Comments

@mattfel1
Copy link
Member

For example, can we do something like:

def innerProdMatMult(tileA: SRAM2[T], tileB: SRAM2[T], tileC: SRAM2[T]): Void = {
  Foreach(...){...} // fill tileC using inner products
}

def outerProdMatMult(tileA: SRAM2[T], tileB: SRAM2[T], tileC: SRAM2[T]): Void = {
  Foreach(...){...} // fill tileC using outer products
}

Accel{ 
  ...
  innerProductMatMult(tileA, tileB, tileC) (innerProductMatMult, outerProductMatMult)
  ...
} 
@mattfel1
Copy link
Member Author

This may be problematic with Spatial's staging. Maybe you can use blackboxes as containers for kernel switching since those won't get dropped. Maybe there can be a generic BlackBoxUse node and store the possible drop-in replacements as Parameter metadata

@David-Durst
Copy link

To add some more motivation: Aetherling (https://github.com/David-Durst/embeddedHaskellAetherling) has multiple options for the same operation with different performance-resources trade-offs. This feature would allow treating both options as a single operator that can be configured by HM,

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

No branches or pull requests

2 participants