From: Ian Lance Taylor
Date: Tue, 27 Jan 2009 13:16:31 -0800
> A co-worker of mine at Google did some experiments along those lines
> using gold. He was not able to demonstrate any performance
> improvements, unfortunately (x86_64 target, proprietary test cases).
> He was hacking linker scripts.
Joern Rennecke writes:
> So I was wodering if we could get a good first-order approximation
> by placing library code that is called frequently together with the
> code that is calling it.
A co-worker of mine at Google did some experiments along those lines
using gold. He was not able to demons
On Tue, Jan 27, 2009 at 6:41 AM, Joern Rennecke wrote:
>
> The remaining question is how to best get the information from the
> compiler proper (cc1 / cc1plus etc) to the linker.
> Should the compiler write a temporary file, which is then read by the
> compiler driver to construct the link line?
>
When benchmarking, there is often noise from semi-random cache
layout issues. If the program in question has a code working set
size that fits in the instruction cache, I this nose can be mostly
attributed to thrashing because of unfortunate code layout.
If we could lay out the code working set
