Skip to content

Remove some out of date TO-DO and comments in rr_graph.cpp #1995

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

Open
vaughnbetz opened this issue Mar 10, 2022 · 5 comments
Open

Remove some out of date TO-DO and comments in rr_graph.cpp #1995

vaughnbetz opened this issue Mar 10, 2022 · 5 comments
Assignees

Comments

@vaughnbetz
Copy link
Contributor

I think there are some out of date comments from the refactoring of the rrgraph apis in rr_graph.cpp (and perhaps related files).

E.g.:

rr_graph.cpp:
/* TODO: The casting will be removed when RRGraphBuilder has the following APIs:
* - set_node_cost_index(RRNodeId, int);
* - set_node_type(RRNodeId, t_rr_type);
*/

(seems to be done).

rr_graph2.cpp:

* TODO: these building functions should only talk to a RRGraphBuilder object

  • TODO: these building functions should only talk to a RRGraphBuilder object
  •   The biggest and fatal issue is 
    
  •   - the rr_graph2.h is included in the rr_graph_storage.h,
    
  •     which is included in the rr_graph_builder.h
    
  •     If we include rr_graph_builder.h in rr_graph2.h, this creates a loop
    
  •     for C++ compiler to identify data structures, which cannot be solved!!!
    
  •     This will block us when putting the RRGraphBuilder object as an input arguement 
    
  •     of this function
    

*/

These should be cleaned up.

@tangxifan
Copy link
Contributor

@vaughnbetz Thanks for pointing this out. I will assign this to the team and create related pull requests.

@tangxifan
Copy link
Contributor

@behzadmehmood-rs Can you arrange the team on cleaning up the code comments and create PRs? If you have anything unclear, just let me know. I will review your PR once it is available.

@behzadmehmood-rs
Copy link
Contributor

@behzadmehmood-rs Can you arrange the team on cleaning up the code comments and create PRs? If you have anything unclear, just let me know. I will review your PR once it is available.

Sure, we will do that @tangxifan.

Copy link

This issue has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you believe this is still an issue, please add a comment.

@github-actions github-actions bot added the Stale label May 18, 2025
@vaughnbetz
Copy link
Contributor Author

@amin1377 @soheilshahrouz : these still look like good cleanups to do, although probably best to do after the openFPGA branch merge so we don't create work for ourselves. Let me know if one of you wants to take a crack at these.

@github-actions github-actions bot removed the Stale label May 20, 2025
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

3 participants