http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51655
Bug #: 51655
Summary: FAIL: c-c++-common/tm/memcpy-1.c (test for excess
errors)
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: domi...@lps.ens.fr
CC: al...@redhat.com
Host: x86_64-apple-darwin10
Target: x86_64-apple-darwin10
Build: x86_64-apple-darwin10
On x86_64-apple-darwin10 the test c-c++-common/tm/memcpy-1.c fails with
FAIL: c-c++-common/tm/memcpy-1.c (test for excess errors)
Excess errors:
/opt/gcc/work/gcc/testsuite/c-c++-common/tm/memcpy-1.c:8:12: error: unsafe
function call '__inline_memcpy_chk' within 'transaction_safe' function
/opt/gcc/work/gcc/testsuite/c-c++-common/tm/memcpy-1.c:8:12: error: unsafe
function call '__builtin___memcpy_chk' within 'transaction_safe' function
/opt/gcc/work/gcc/testsuite/c-c++-common/tm/memcpy-1.c:8:12: error: unsafe
function call '__builtin_object_size' within 'transaction_safe' function
/opt/gcc/work/gcc/testsuite/c-c++-common/tm/memcpy-1.c:8:12: error: unsafe
function call '__builtin_object_size' within 'transaction_safe' function
I also see the failures reported in pr51124:
Running target unix/-m32
FAIL: libitm.c/memcpy-1.c execution test
FAIL: libitm.c/memset-1.c execution test
WARNING: libitm.c++/static_ctor.C compilation failed to produce executable
...
Running target unix/-m64
WARNING: libitm.c++/static_ctor.C compilation failed to produce executable
due to
libitm: pr_undoLogCode not supported
FAIL: libitm.c/memcpy-1.c execution test
...
libitm: pr_undoLogCode not supported
FAIL: libitm.c/memset-1.c execution test
...
XFAIL: libitm.c++/static_ctor.C (test for excess errors)
Excess errors:
/opt/gcc/work/libitm/testsuite/libitm.c++/static_ctor.C:12:18: error: unsafe
function call 'void __cxa_guard_release(long long int*)' within
'transaction_safe' function
/opt/gcc/work/libitm/testsuite/libitm.c++/static_ctor.C:12:18: error: unsafe
function call 'int __cxa_guard_acquire(long long int*)' within
'transaction_safe' function
