The-OpenROAD-Project / The-OpenROAD-Project/OpenROAD
openroad should write it's commands into the log
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Verilog
- Stars
- 3.1k
- Forks
- 1k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 136
Description
Description
Revisiting a year old log files, it would have been very helpful to have the CMD's that were issued to be in the log file.
Suggested Solution
write CMD's into the log file
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests, so start by locating OpenROAD's command-dispatch and logging entry points. Confirm how issued CMDs are represented, then verify that commands appear in the log when a flow runs; the issue is done when later log readers can see those commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100