Conversation
- Add PE ID system with PE(id) as keys - Organize instructions by PE coordinates (x, y) - Calculate data movement directions (N, S, E, W, NE, SE, NW, SW, Local) - Include complete instruction information (opcode, time_step, src_tile, dst_tile, operands) - Support constant value extraction - Generate structured JSON output for PE instructions
- Add example JSON output showing PE-based instruction organization - Demonstrates the structure with PE(id) keys and coordinate information - Shows complete instruction details including directions and time steps - Serves as reference for the code generation pass output format
…obust mapping handling
…source direction calculation
…prove return operation handling
|
@ShangkunLi any idea why the build time out? no changes related to mapper in this PR. |
|
Great, I still need more time to fix those errors. And I need to discuss some issue with @Jackcuii |
@n0thingNoob @tancheng I built and ran the code in this branch locally, the segment faults seem to come from the |
ok, let me check what happened. |
@ShangkunLi How can I run the same test locally? I want to see what happened to my code |
Line 51 in 493f4cb dataflow/test/neura/ctrl/branch_for.mlir Lines 32 to 38 in 493f4cb |
|
Looks like my revision passed. I can keep working on other issues. |
You still need to check your functionality in some tests like this dataflow/test/neura/ctrl/branch_for.mlir Lines 31 to 40 in 493f4cb |
Yes, I am working on that. |
|
Updates: removed redundant IR walk() calls and unified traversal into a single function-level pass. Also standardized variable and function names (need reviews) @tancheng |
tancheng
left a comment
There was a problem hiding this comment.
Great job Yijia~!
Plz fix the comments style and variable naming convention. Also, plz let me click on the "solve" once you fix all of them. Thanks.
Will do it ASAP. And for the last question: |
This is the old README file for the test case
|
I am not sure why there is a conflict when pushing the first commit. I merged the latest main into architecture_spec to resolve it and removed the obsolete README that was only used by the old test. @tancheng |
I didn't get it. Will you provide a README or not? |
Perhaps not, the branch test is a little bit complicated. Is the README necessary for this test? |
Hi @n0thingNoob, I just meant to have simple explanation maybe about only one tile for two time steps. You don't need explain what happen on all the tiles across all time steps. How does this sound? You can put your README.md back in your test folder, like what @HobbitQia (https://github.com/coredac/dataflow/tree/main/test/visualize) and @ShangkunLi (https://github.com/coredac/dataflow/tree/main/test) did. Sounds good to you? |
Sure. |
|
You are aware of your always failed test, right? https://github.com/coredac/dataflow/actions/runs/17523525173/job/49770978606 And it should be an easy fix for you I think. |
Working on it. |
|
okay to merge now @n0thingNoob? or anything else you want to fix? |
Yes, let's do it for now. |
Current work
Future Enhancements Needed
Testing
Files Changed