public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Revital Eres <revital.eres@linaro.org>
To: Ayal Zaks <ZAKS@il.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, SMS] Fix violation of memory dependence
Date: Tue, 14 Jun 2011 09:21:00 -0000	[thread overview]
Message-ID: <BANLkTinLTui=+GE4hW4sAPqsLi8KTpU6NQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=qFfk0agRBwe5LEW=9m7cjwhE6EQ@mail.gmail.com>

Hello,

>> You could check first thing if (from->cuid == to->cuid), for code clarity.
>
> I will address this point separately and commit the current version of
> the patch as is if that's OK.

Re-thinking about that, I'll prepare a new version of the patch which
addresses this and re-send it.

Sorry for the confusion,
Revital

  reply	other threads:[~2011-06-14  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13  9:13 Revital Eres
2011-06-14  8:31 ` Ayal Zaks
2011-06-14  8:44   ` Revital Eres
2011-06-14  9:21     ` Revital Eres [this message]
2011-06-16  6:27   ` Revital Eres
2011-06-15 23:07     ` Ayal Zaks
2011-06-16  5:41       ` Revital Eres

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='BANLkTinLTui=+GE4hW4sAPqsLi8KTpU6NQ@mail.gmail.com' \
    --to=revital.eres@linaro.org \
    --cc=ZAKS@il.ibm.com \
    --cc=gcc-patches@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: 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).