Now that I got my spiffy new x86_64 super-box I thought I’d revisit callcatcher and binfilter shrinkage again now that it doesn’t take a year to continually rebuild binfilter until callcatcher stops listing unused methods. So I added x86_64 support and gave it a whirl.
Results are a little disappointing I guess, original size of final stripped binfilter deliverables were 20376k, and after callcatcher stripping 19892k, so only 484k smaller final binary size. I was hoping for a full meg, but while binfilter should have been a fertile ground for finding used code, much of the unused code had already been stubbed out to be just bool unused {return false;}.
I did find a pair of nice catches though, Uncallable dtor’s where the constucted objects are deleted through a base pointer of their ancestor which has no virtual methods. And a neato if ( bOldVisible && !bOldVisible ) { do stuff; }
Caolan,
I really appreciate your work on OOo for x86_64. I’m using your build on my system. It’s working great. It’s very fast. I use it for serious stuff.
I remember maybe in the days of FC3 somebody wrote that OOo for x86_64 is not to be expected soon, maybe in FC6 or so. It sounded like far far in the future. Now FC6 is being worked on, and the native OOo is still not in the fedora-devel repository.
I believe it’s about time that the native OOo is pushed to fedora-devel. The only way to iron out bugs in this large project is to ask users for help. Those using fedora-devel are ready to help. They are prepared to deal with breakage. They want the next FC release to be the best.
Please don’t let another Fedora Core to be released with 32-bit-only OOo.