public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/52142] New: [trans-mem] inlined transaction_pure functions are instrumented
@ 2012-02-06 21:21 patrick.marlier at gmail dot com
  2012-02-06 21:35 ` [Bug middle-end/52142] " patrick.marlier at gmail dot com
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: patrick.marlier at gmail dot com @ 2012-02-06 21:21 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 52142
           Summary: [trans-mem] inlined transaction_pure functions are
                    instrumented
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: patrick.marlier@gmail.com
                CC: aldyh@gcc.gnu.org, rth@gcc.gnu.org


Created attachment 26592
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26592
testcase with -fgnu-tm -O1

In this testcase, the function 'purefunc' has inline and transaction_pure
attribute. In the optimized mode (-O), the function becomes inlined but also
instrumented whereas it was annotated transaction_pure.


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

end of thread, other threads:[~2012-02-15  0:30 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-06 21:21 [Bug middle-end/52142] New: [trans-mem] inlined transaction_pure functions are instrumented patrick.marlier at gmail dot com
2012-02-06 21:35 ` [Bug middle-end/52142] " patrick.marlier at gmail dot com
2012-02-07  9:28 ` rguenth at gcc dot gnu.org
2012-02-07 17:53 ` rth at gcc dot gnu.org
2012-02-14 15:15 ` aldyh at gcc dot gnu.org
2012-02-14 17:50 ` rth at gcc dot gnu.org
2012-02-15  0:29 ` aldyh at gcc dot gnu.org
2012-02-15  0:30 ` 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).