public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/47492] New: problem with memset() inside transaction_safe function
@ 2011-01-27 15:10 vasilis.karakostas at bsc dot es
  2011-01-27 15:19 ` [Bug c/47492] [trans-mem] Problem " patrick.marlier at gmail dot com
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: vasilis.karakostas at bsc dot es @ 2011-01-27 15:10 UTC (permalink / raw)
  To: gcc-bugs

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

           Summary: problem with memset() inside transaction_safe function
           Product: gcc
           Version: trans-mem
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vasilis.karakostas@bsc.es
                CC: aldyh@redhat.com, javier.arias@bsc.es,
                    patrick.marlier@gmail.com


Created attachment 23141
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23141
testcase

When I call memset() function from an __attribute__((transaction_safe))
function, I get compilation error.

testcase.c:10:2: error: unsafe function call 'memset' within 'transaction_safe'
function

According to Intel TM ABI, the memset() function is managed by the compiler and
it should be automatically transformed to be transaction safe.
I have attached an example.


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

end of thread, other threads:[~2011-02-03 16:41 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-27 15:10 [Bug c/47492] New: problem with memset() inside transaction_safe function vasilis.karakostas at bsc dot es
2011-01-27 15:19 ` [Bug c/47492] [trans-mem] Problem " patrick.marlier at gmail dot com
2011-01-31 18:57 ` aldyh at gcc dot gnu.org
2011-02-03 16:41 ` aldyh 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).