public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/55401] New: uninstrumented path in TM clones are still instrumented Date: Mon, 19 Nov 2012 21:51:00 -0000 [thread overview] Message-ID: <bug-55401-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55401 Bug #: 55401 Summary: uninstrumented path in TM clones are still instrumented Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: aldyh@gcc.gnu.org If a transaction appears in a TM clone, the uninstrumented path still gets instrumented. Example: int george; int ringo; __attribute__((transaction_callable)) void q1() { ringo=666; __transaction_atomic { george=999; } } Generated code: <bb 2>: _8 = 666; __builtin__ITM_WU4 (&ringo, _8); tm_state.5_11 = __builtin__ITM_beginTransaction (43); _12 = tm_state.5_11 & 2; if (_12 != 0) goto <bb 3>; else goto <bb 4>; <bb 3>: _13 = 999; __builtin__ITM_WU4 (&george, _13); __builtin__ITM_commitTransaction (); goto <bb 5>; <bb 4>: _15 = 999; __builtin__ITM_WU4 (&george, _15); __builtin__ITM_commitTransaction (); <bb 5>: return;
next reply other threads:[~2012-11-19 21:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-19 21:51 aldyh at gcc dot gnu.org [this message] 2012-11-19 21:52 ` [Bug middle-end/55401] " aldyh at gcc dot gnu.org 2012-11-29 1:11 ` aldyh at gcc dot gnu.org 2012-12-03 16:12 ` aldyh at gcc dot gnu.org 2012-12-04 0:25 ` 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-55401-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).