From: Patrick Marlier <patrick.marlier@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Torvald Riegel <triegel@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Henderson <rth@redhat.com>
Subject: Re: [trans-mem] Explicitly go irrevocable even if transaction will always go irrevocable.
Date: Fri, 28 Oct 2011 14:51:00 -0000 [thread overview]
Message-ID: <4EAABC67.6050201@gmail.com> (raw)
In-Reply-To: <4EAAA5C1.9040305@redhat.com>
On 10/28/2011 08:53 AM, Aldy Hernandez wrote:
> If the original test was not wrong, you need to add a new test (and
> bonus points for finding out why this test is currently failing :)).
long g, xxx, yyy;
/* { dg-final { scan-tree-dump-times "transforming: .*_ITM_RaWU8
\\(&g\\);" 1 "tmmemopt" } } */
At least, maybe one of the problem is that g is "long" type (4 bytes on
32bits) and it is testing for 8 bytes?
Patrick.
next prev parent reply other threads:[~2011-10-28 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 10:35 Torvald Riegel
2011-10-28 13:56 ` Aldy Hernandez
2011-10-28 14:51 ` Patrick Marlier [this message]
2011-10-29 15:36 ` Torvald Riegel
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=4EAABC67.6050201@gmail.com \
--to=patrick.marlier@gmail.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=triegel@redhat.com \
/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: link
Be 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).