public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "machens at tuhh dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59130] New: Inline(d) or static functions not registered in transactional clone table Date: Thu, 14 Nov 2013 14:05:00 -0000 [thread overview] Message-ID: <bug-59130-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59130 Bug ID: 59130 Summary: Inline(d) or static functions not registered in transactional clone table Product: gcc Version: 4.7.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: machens at tuhh dot de Created attachment 31218 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31218&action=edit Test case to reproduce the bug When a function pointer is used in a transactional section to call a function the STM library (such as libitm) has to lookup the corresponding transactional function 'clone' of that function. The compiler therefore generates mapping tables which associate function pointers of non-transactional functions with their corresponding transactional function clones. With the STAMP benchmark suite I have experienced that the compiler does not generate entries in the lookup table for functions which are declared as static or inline. I have written a small test case to reproduce the bug (see attachment). Compile with: /usr/bin/g++-4.7 -fgnu-tm -Wall -g -O3 -o gnutm-test main.cpp -lpthread -litm
reply other threads:[~2013-11-14 14:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-59130-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).