profiler_unittest failing always in new ppc64le architecture and frequently in x86

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Take the latest git source 
2. Did autoreconf -f -i, to apply the patches of the new architecture ppc64le 
for the autotools ( config.guess and libtool ) 
3. Build the package as configure/make.
4. The make check has the following test failure in profiler_unittest.sh in 
ppc64le architecture.
5. This test failure is also observed sometimes in x86 architecture as well

What is the expected output? What do you see instead?

The test results I see 
>>> profile doesn't match, args: 
/home/rajesh/gperftools/gperftools/.libs/lt-profiler1_unittest 
/tmp/profile_info/p12 vs.  /tmp/profile_info/p13
>>> Diff:
11c11
<        0   0.0% 100.0%        1   2.4% 00000024.plt_call.__gmon_start__

---
>        0   0.0% 100.0%        1   2.4% 0x0000000000000000

PROFILE: interrupts/evictions/bytes = 71/0/4272
Using local file /home/rajesh/gperftools/gperftools/.libs/lt-profiler3_unittest.
Using local file /tmp/profile_info/p14.
Using local file /tmp/profile_info/p15.
Using local file /tmp/profile_info/p15.

>>> profile doesn't match, args: 
/home/rajesh/gperftools/gperftools/.libs/lt-profiler3_unittest 
/tmp/profile_info/p14 vs.  /tmp/profile_info/p15
>>> Diff:
12c12
<        0   0.0% 100.0%        1   1.4% 00000024.plt_call.__gmon_start__

---
>        0   0.0% 100.0%        1   1.4% 0x0000000000000000

PROFILE: interrupts/evictions/bytes = 73/0/2352
uPROFILE: interrupts/evictions/bytes = 91/0/2288
Using local file /home/rajesh/gperftools/gperftools/.libs/lt-profiler3_unittest.
Using local file /tmp/profile_info/p16.
Using local file /home/rajesh/gperftools/gperftools/.libs/lt-profiler3_unittest.
Using local file /tmp/profile_info/p17.
PROFILE: interrupts/evictions/bytes = 24/0/1992
PROFILE: interrupts/evictions/bytes = 25/0/2088
PROFILE: interrupts/evictions/bytes = 24/0/2080
Tests finished with 2 failures

Sometimes, there profiler_unittest testcase fails with 1 failure in 
profiler3_unittest.

Does the nature of this test failures are just characteristics of system loads 
or any functional failures.
If this is any functional failure should there any patches applied.
Can anyone comment about the severity of this test failure?

What version of the product are you using? On what operating system?

The latest source from the git repository (2.2).
The operating system under use is Ubuntu 14.04

Please provide any additional information below.

Original issue reported on code.google.com by mailtora...@gmail.com on 30 May 2014 at 11:18

[GoogleCodeExporter]

Hi,

This issue is not severe, it is not an error in the profiler it is a compiler 
error.
With a newer version of GCC it should work. I tried GCC 4.9 and 4.8.3 and this 
test passed multiple times.

Regards,
Raphael

Original comment by rajntm...@gmail.com on 27 Jun 2014 at 12:16