This is my (in)activity log. You might like to visit my employer
Novell which is an amazing company, and also
Dell who in days of yore provided me with a
free laptop for Gnome development / conferences.
Also if you have the time to read this sort of stuff you could enlighten
yourself by going to Unraveling Wittgenstein's net or if
you are feeling objectionable perhaps here.
Stuff Michael Meeks is doing
- Full build died at start, with a missing patch - bother.
Did more measurements on libsvx - annoyingly -Bsymbolic-functions is
a higher impact change than vtrelocs:
Of course, a large proportion of OO.o startup is dominated
by the cost of linking, in particular unique named relocation
processing, around ~20% of the time; so extrapolating wildly,
10k -> 2k is a 5x speedup, yielding a ~15% CPU-time startup
win. Or, with just -Bsymbolic-functions an overall 12% win.
|variant ||size ||unique named relocs ||fn / thunk unique named relocs|
|current ||10154324 ||10375 ||6650, 1718|
|-Bsymbolic-functions ||10020556 ||3891 ||1404, 481|
|-Bsym + vtrelocs ||9840180 ||2135 ||37, 0|
- Amused by the onslaught of 'virtual' as a new marketing
term: it's no longer a thin-client, its a "virtual display client",
its no longer a 'pencil' but a "virtual marking solution" etc. Of
course when there are already several other marketing terms in a
product name it could become increasingly difficult to understand:
eg. is a plain-old Xserver a "virtual java desktop display
client solution" ?
- Comparing reloc runs is much helped by
echo "0" > /proc/sys/kernel/randomize_va_space.
Found I wasn't linking the new libsvx correctly, fixed that. Of
course the real benefit of vtrelocs is (having switched virtual
function calls to going via the relevant vtable) not exporting any
virtual symbols / thunks; but that's for the future.
- Kicked off a full build of OO.o with the various new
options, persuaded svn to update apply (it has the unfortunate weakness
of failing to fully update, but retaining the same final status
message). OO.o build fell-foul of cppu's gcc3.map hiding some
vtables it shouldn't. Poked at pulling my iogrind / valgrind snapshot
up to the lastest version, breaking it, bother. Some debugging of
my evo. alarm issue.
In case it's not painfully obvious: the reflections reflected here are my
own; mine, all mine ! and don't reflect the views of Novell, The
Lithuanian Gov't or Arnold Schwarzenegger. It's also important to
realise that I'm not in on the Swedish Conspiracy.
Occasionally people ask for formal photos for conferences,
Michael Meeks (email@example.com)