public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "patrick.marlier at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libitm/53008] abort in _ITM_getTMCloneSafe Date: Tue, 15 May 2012 22:32:00 -0000 [thread overview] Message-ID: <bug-53008-4-fzKQpWMV4c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53008-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53008 --- Comment #5 from Patrick Marlier <patrick.marlier at gmail dot com> 2012-05-15 22:23:54 UTC --- Created attachment 27412 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27412 testcase for gcc testsuite The problem is not into libitm. Attached a testcase for testsuite (gcc/testsuite/gcc.dg/tm/indirect-3.c). Note that with your patch, the tm testsuite fails. pr51516.C fails because the original function is output and not only the clone (only the clone is required). I am not sure the way to properly fix it. Thanks for having a look at the problem! -- Patrick Marlier
next prev parent reply other threads:[~2012-05-15 22:24 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-16 15:08 [Bug libitm/53008] New: " daveboutcher at gmail dot com 2012-04-18 17:47 ` [Bug libitm/53008] " daveboutcher at gmail dot com 2012-04-27 15:00 ` patrick.marlier at gmail dot com 2012-05-08 23:24 ` daveboutcher at gmail dot com 2012-05-15 16:50 ` torvald at gcc dot gnu.org 2012-05-15 22:32 ` patrick.marlier at gmail dot com [this message] 2012-05-16 2:12 ` daveboutcher at gmail dot com 2012-05-22 15:59 ` [Bug ada/53008] " aldyh at gcc dot gnu.org 2012-05-22 16:11 ` patrick.marlier at gmail dot com 2012-05-22 17:38 ` [Bug middle-end/53008] " aldyh at gcc dot gnu.org 2012-05-25 17:29 ` aldyh at gcc dot gnu.org 2012-05-30 22:15 ` aldyh at gcc dot gnu.org 2012-05-30 22: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-53008-4-fzKQpWMV4c@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).