Automatic rewriting uses as much CPU as you can throw at it… a full automatic rewriting pass takes about an hour on this 8-core machine.
This entry was posted on 24 Apr, 2008 at 11:47 am and is tagged with , cpu, garburator.
Is there anywhere I could view/browse those rewritten pieces of source code?
An infinite number of monkeys require processor time.
Here’s a stupid question forya: What are you rewriting?
And once again, CPU6 is being a slacker. *shakes head*
David, I am doing the XPCOMGC rewrites. There are three rewrites in the series:
* garburator implemented using oink/elsa
* GCObject inheritance implemented using dehydra and text processing
* remove-addrefs implemented using text processing
A single script runs these three all in a row without human intervention. If you want to see an example of the results, see the three “automatic-*” files from a previous revision. Caution: the patches are almost 200k lines, 20+MB a piece.
For more information about Mozilla’s automatic rewriting projects in general, see Taras and David Mandelin‘s blogs, and the mozilla.dev.static-analysis newsgroup.
Just curious, but can you apply the patches and compile and run the build or is the MMgc stuff not set up yet?
I wonder how this load would run on a Sun UltraSPARC T2 box. Say a dual socket 1.4GHz rig. That gives you 128 threads at 8 cores/socket and 8 threads/core. Seeing as how the load is probably memory and integer intensive only, the fit would probably be pretty good.
An hour for a full rewriting pass… and how long to fry an egg on that box?
Mail (will not be published)