Issue #76
Error: file.v:3580: Cloning should have already been done bottom-up
| Status: | Closed | Start: | 04/06/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | Wilson Snyder | % Done: | 0% |
|
| Category: | TranslationError | |||
| Target version: | - | Estimated time: | 1.00 hour |
Description
I have been evaluating the latest release of Verilator and have come across an error (during translation) which I don't understand. I was wandering if you could explain the meaning of this error.
%Error: file.v:3580: Cloning should have already been done bottom-up
History
Updated by Wilson Snyder over 1 year ago
- Status changed from New to Assigned
I looked at your tree file and some of the calculated levels seem incorrect. I don't see use of txsif_reg. Is that used? Are you using the --top-module option? If so I think that might be related.
Updated by Wilson Snyder over 1 year ago
- Status changed from Assigned to Resolved
- Estimated time set to 1.00
Please try the git version. I didn't reproduce the error message, but did see an error in sorting the module order which could cause it, assuming you're using -y or --top-module.
Updated by Dimitris Nalbantis over 1 year ago
I edited the tree file manually so it is likely I have accidentaly removed the txsif_reg module declaration. I checked it exists in the original file. The second tree file I sent you is a second take on the same task and the txsif_reg module is included.
I do use --top-module. I tried to access the git version but my Linux environment is inside a secure network and git is not allowed to access the given http address. Is it possible to pack the git version in a tar file and make it available somewhere where I can download from my PC and put it in the secure network as a normal tar file and built it inside the secure network?
Updated by Wilson Snyder over 1 year ago
- File bug76.patch added
Try the enclosed patch. For next time, perhaps you could download it via your home machine?
Updated by Dimitris Nalbantis over 1 year ago
That seems to have solved the problem I was having. Many thanks for your prompt response.
![[logo]](/img/veripool_small.png)