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
On Thu, Aug 27, 2009 at 3:51 AM, Jeff Johnson wrote:
> I'm using helgrind from 3.5.0 on OPENMP code.
>
> I have a lazily malloc'd pthread mutex in a static global
> variable that helgrind detects.
>
> I'd like to disable the warning somehow in code, not
> with a suppression, so that I can look at m
Hi:
I tried run Valgrind without any tool on SPEC2006.
There are two benchmarks that have problem running with Valgrind.
One is 434.zeusmp, which reports failure of mmap by valgrind.
The other is 447.dealII, which does not stop after 2 days. The native
execution is only about 520 seconds.
My syst
On Aug 27, 2009, at 9:33 AM, Julian Seward wrote:
>
>> I'm using helgrind from 3.5.0 on OPENMP code.
>>
>> I have a lazily malloc'd pthread mutex in a static global
>> variable that helgrind detects.
>>
>> I'd like to disable the warning somehow in code, not
>> with a suppression, so that I can l
> I'm using helgrind from 3.5.0 on OPENMP code.
>
> I have a lazily malloc'd pthread mutex in a static global
> variable that helgrind detects.
>
> I'd like to disable the warning somehow in code, not
> with a suppression, so that I can look at more interesting
> errors.
You can't use Helgrind pr