Thanks Tom,
One of the options is to fuse the new sections into one big ".text".
gcc-help suggested using ld's linker script to achieve this.
This does help with the function names in stack traces.
Do you see any trouble with this (other than a performance hit) ?
Is a similar treatment required f
On 26/08/09 15:13, Madhan Sadasivam wrote:
> When intel compiler is used with profiler guided optimization,
> two new sections called "text.hot" and "text.unlikely" are
> created by the compiler. This is on Linux x86 32 bit.
>
> The symbols in these sections are not read by Valgrind
> and this cau
Thanks for helping me John, here's the output
Sections from .o file:
There are 19 section headers, starting at offset 0x378b0:
Section Headers:
[Nr] Name TypeAddr OffSize ES Flg Lk
Inf Al
[ 0] NULL 00 00 00
> When intel compiler is used with profiler guided optimization,
> two new sections called "text.hot" and "text.unlikely" are
> created by the compiler. This is on Linux x86 32 bit.
Please show the relevant data from
readelf --sections foo.o
readelf --segments my_app
for an ET_REL object
Hello,
When intel compiler is used with profiler guided optimization,
two new sections called "text.hot" and "text.unlikely" are
created by the compiler. This is on Linux x86 32 bit.
The symbols in these sections are not read by Valgrind
and this causes many frames in memcheck error stack traces
