public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/47747] New: [trans-mem] unsafe virtual function not properly displayed
@ 2011-02-15  8:03 patrick.marlier at gmail dot com
  2011-02-16 16:14 ` [Bug c++/47747] " aldyh at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: patrick.marlier at gmail dot com @ 2011-02-15  8:03 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47747

           Summary: [trans-mem] unsafe virtual function not properly
                    displayed
           Product: gcc
           Version: trans-mem
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: patrick.marlier@gmail.com
                CC: rth@gcc.gnu.org, aldyh@gcc.gnu.org


Created attachment 23348
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23348
testcase that shows the error

If a virtual function is not annotated as transaction safe and called in a
transaction safe function, gcc raises an unsafe function error but it doesn't
print correctly the function name.

$ g++ -fgnu-tm -S -O0 unsafe_virtual.i 
unsafe_virtual.i: In constructor ‘Building::Building(InputStream*)’:
unsafe_virtual.i:17:30: error: unsafe function call ‘#‘obj_type_ref’ not
supported by dump_decl#<declaration error>’ within ‘transaction_safe’ function

Attached a testcase.

Patrick Marlier.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-11-21 22:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-15  8:03 [Bug c++/47747] New: [trans-mem] unsafe virtual function not properly displayed patrick.marlier at gmail dot com
2011-02-16 16:14 ` [Bug c++/47747] " aldyh at gcc dot gnu.org
2011-03-07 16:19 ` aldyh at gcc dot gnu.org
2011-11-21 23:12 ` torvald at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).