kimm240
kimm240
@wrongtest-intellif This PR implements the extension for other epilogue forms (ReLU/Clipping) as discussed in the previous PR #18418 review conversation.
What you say is definitely good direction! In `compute_inline.cc`, usual data flow reconnection method is used to handle complex operations using Index mapping with DetectInterMap and substitution logic after BufferLoad...
I completely agree. However, implementing a full, general Data Flow Reconnection logic requires significant development time and extensive testing. Given that the current PR is functionally complete and stable, and...
@yongwww Hello. Sorry for dup PR. (dup: https://github.com/apache/tvm/pull/18173) This is because I'm inexperienced with sending PRs. This PR extend FuseOps to handle operator fusion issue.
@yongwww Hi, just a gentle ping on this PR. Please let me know if anything needs clarification or modification. Thanks for your time!
@wrongtest-intellif This Pull Request (PR) extends the activation function support, following the footsteps of [https://github.com/apache/tvm/pull/18418](https://www.google.com/search?q=https://github.com/apache/tvm/pull/18418), which originally added ReLU support to the FuseReductionEpilogue primitive in the Apache TVM repository. Furthermore,...
@chentong319 Yes, currently: - MatMul → Linalg (from PR #3343) - EntryPoint & others → Krnl path I agree that selective per-op conversion would be beneficial. Is there any direction...