Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I've been doing this for years to keep my git repositories clean, but I realized that others may not know that a little maintenance is good for your git repositories.
Here's what I do every few months. For those that just do a pull to keep current with development it probably won't create as much of a change in the repository size, but Steve and any others who are submitting patches should notice a difference possibly a significant difference.
1. If you have code that has not been committed or merged to github make sure you are either brave or have a current backed up. I don't want you to loose any hard work.
2. Go to the top iverilog directory and do a du -sh so you have a base line size.
3. Run git fsck to see if there are any problems.
4. Run git gc --aggressive this cleans the repository.
5. Run git fsck again to verify that any reported problems are resolved. If not there may be some real corruption in your git repository.
6. Run du -sh again to see the current size. I have seen this be half the original value!
7. Repeat 2 - 6 for the ivtest and any other iverilog directories you may have.
All this takes a few minutes on my laptop which has two copies of iverilog and ivtest (each has one for working and one for pushing).
I hope this is useful,
Accellera may be starting a WG to look at getting better language interoperability. This probably means developing APIs so different simulators can work together (otherwise I'm not sure what the WG will do). See attached PPT.
This is good from an open-source perspective because it means you don't have to do everything in your own simulator, you can potentially partition the problems of DUT simulation and testbench, and you could have (say) SystemC as the testbench and Icarus managing the DUT.
Note: this is being driven by EDA customers rather than vendors (who probably don't like the idea).