On Mon, 05 Apr 2010 15:43:02 -0700I'm sorry that you don't find this interesting. I did not suggest that people compile their own browser to get a perfect layout. This is something that Mozilla can do when preparing builds and it's also something distributions can do. It just so happens that large parts of startup will be very similar for every single firefox install, might as well layout the binary accordingly.
Taras Glek<tglek@xxxxxxxxxxx> wrote:
To make matters worse,Yes, the linker scrambles the executable's block ordering.
the compile-time linker + gcc lay out code in a manner that does not
correspond to how the resulting executable will be executed(ie the
layout is basically random).
This just isn't an interesting case. World-wide, the number of people
who compile their own web browser and execute it from the file which ld
produced is, umm, seven.
So I'd suggest that you always copy the executable to a temp file andYou mean to get it into a cache or to hope to avoid fragmentation? If you are suggesting this to avoid measuring the startup overhead of paging the binary in, I strongly disagee. It is the slowest part of firefox startup and needs to be addressed.
mv it back before running any timing tests.