public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vasilis.karakostas at bsc dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/47492] New: problem with memset() inside transaction_safe function Date: Thu, 27 Jan 2011 15:10:00 -0000 [thread overview] Message-ID: <bug-47492-4@http.gcc.gnu.org/bugzilla/> (raw) 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.
next reply other threads:[~2011-01-27 14:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-27 15:10 vasilis.karakostas at bsc dot es [this message] 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
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-47492-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).