Comment 5 for bug 1276262

On my PC, running oneiric, version 11.10, on Xeon, with gcc 4.6.1, I also see errors when testing Boost v1.55.
EXIT STATUS are:
      1 : 11 (False results)
134 : 1 (Exception, aborted)
139 : 2 (Seg Fault)
200 : 10 (memory access violation)
201 : 8 (error detected)

I have to find a x86 machine I can install with a fresh Ubuntu. No time for doing that for now, but I'll do.

When comparing what I get on PPC/LE and my PC, about most important errors (seg fault, memory acces, exception aborted), I have:
- Errors on both environments:
   ES 134:
      ../bin.v2/libs/spirit/test/qi_match_manip1-p3.test/gcc-4.8/debug/phoenix_v3-on/qi_match_manip1-p3.output
   ES 139:
      ../bin.v2/libs/spirit/test/lex_lexertl2-p3.test/gcc-*/debug/phoenix_v3-on/lex_lexertl2-p3.output
     ../bin.v2/libs/filesystem/test/operations_test_static.test/gcc-*/debug/link-static/operations_test_static.output
   ES 200:
     ../bin.v2/libs/heap/test/binomial_heap_test.test/gcc-*/debug/threading-multi/binomial_heap_test.output
     ../bin.v2/libs/heap/test/pairing_heap_tests.test/gcc-*/debug/threading-multi/pairing_heap_tests.output
     ../bin.v2/libs/heap/test/skew_heap_test.test/gcc-*/debug/threading-multi/skew_heap_test.output"
     ../bin.v2/libs/heap/test/mutable_heap_test.test/gcc-*1/debug/threading-multi/mutable_heap_test.output"
     ../bin.v2/libs/heap/test/fibonacci_heap_test.test/gcc-*1/debug/threading-multi/fibonacci_heap_test.output"
     ../bin.v2/libs/heap/test/priority_queue_test.test/gcc-*/debug/threading-multi/priority_queue_test.output"

- Errors only on PPC/LE :
   ES 134: NONE
   ES 139:
      ../bin.v2/libs/context/test/test_context.test/gcc-4.8/debug/link-static/test_context.output
      ../bin.v2/libs/coroutine/test/test_coroutine.test/gcc-4.8/debug/link-static/test_coroutine.output
      ../bin.v2/libs/locale/test/test_boundary.test/gcc-4.8/debug/test_boundary.output
   ES 200:
    ../bin.v2/libs/heap/test/d_ary_heap_test.test/gcc-4.8/debug/threading-multi/d_ary_heap_test.output
    ../bin.v2/libs/test/test/prg_exec_fail2.test/gcc-4.8/debug/prg_exec_fail2.output

- Errors only on x86_64:
   ES 200:
     ../bin.v2/libs/heap/test/d_ary_heap_test.test/gcc-4.6.1/debug/threading-multi/d_ary_heap_test.output"

So, there are cores and memory access violations that are specific to PPC/LE.
And there are cores and memory access violations that are common to both environments, though they use different versions of GCC.

I am now building/testing on PPC/BE in order to compare. It uses same version of GCC.