This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/51696] New: [trans-mem] unsafe indirect function call in struct not properly displayed
- From: "patrick.marlier at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 28 Dec 2011 20:38:19 +0000
- Subject: [Bug c/51696] New: [trans-mem] unsafe indirect function call in struct not properly displayed
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51696
Bug #: 51696
Summary: [trans-mem] unsafe indirect function call in struct
not properly displayed
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: patrick.marlier@gmail.com
CC: aldyh@gcc.gnu.org, torvald@gcc.gnu.org
Created attachment 26196
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26196
Attached testcase
With an unsafe indirect function call, the error message is not clear. I don't
know if it can display the declaration. In the worst case, "unsafe indirect
function call within âtransaction_safeâ function" should be ok.
$ ./gcc/xgcc -B./gcc/ -fgnu-tm -O0 testcase.i
testcase.i: In function âfuncâ:
testcase.i:7:21: error: unsafe function call â<Uf3c0>â within
âtransaction_safeâ function
testcase.i:8:12: error: unsafe function call âcompare.1â within
âtransaction_safeâ function
Patrick Marlier.