From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Jayant R. Sonar" <Jayant.Sonar@kpitcummins.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"rth@redhat.com" <rth@redhat.com>
Subject: RE: [Ping] RE: CR16 Port addition
Date: Tue, 04 Oct 2011 16:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1110041546340.8834@digraph.polyomino.org.uk> (raw)
In-Reply-To: <C013F7BFDC93F047B111833D343777BD176C2E29@KCHJEXMB02.kpit.com>
On Tue, 4 Oct 2011, Jayant R. Sonar wrote:
> PING 4: For review
> Hi,
> Can someone please review the patch:
> http://gcc.gnu.org/ml/gcc-patches/2011-05/msg01441.html
Could someone with general back-end expertise look at this? I don't have
the expertise to review whether the back end follows good practice for
back-end implementation (beyond the general sort of issues I reviewed a
previous iteration of this patch for).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-10-04 15:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 9:33 Jayant R. Sonar
2011-10-04 16:06 ` Joseph S. Myers [this message]
2011-10-04 23:13 ` Richard Henderson
2011-10-21 15:28 Jayant R. Sonar
2011-11-04 13:39 Jayant R. Sonar
2011-11-04 16:53 ` Richard Henderson
2011-11-04 20:34 ` Joseph S. Myers
2011-11-28 16:35 ` Jayant R. Sonar
2011-11-28 18:13 ` Joseph S. Myers
2011-11-29 13:44 ` Jayant R. Sonar
2011-11-29 13:54 ` Rainer Orth
2011-11-30 10:50 ` Jayant R. Sonar
2011-12-09 12:47 ` Jayant R. Sonar
2011-12-16 14:07 ` Jayant R. Sonar
2011-12-30 8:32 ` Jayant R. Sonar
2012-01-10 12:55 ` Jayant R. Sonar
2012-01-10 16:03 ` Joseph S. Myers
2012-01-10 23:05 ` Richard Henderson
2012-01-11 12:52 ` Jayant R. Sonar
2012-01-11 20:02 ` Richard Henderson
2012-01-11 20:49 ` Hans-Peter Nilsson
2012-01-11 22:10 ` Joseph S. Myers
2012-01-11 23:23 ` Hans-Peter Nilsson
2012-01-12 11:07 ` Jayant R. Sonar
2012-02-03 4:11 ` Jayant R. Sonar
2012-02-13 6:57 ` Gerald Pfeifer
2012-02-14 7:13 ` Jayant R. Sonar
2012-02-19 16:46 ` Gerald Pfeifer
2012-02-20 15:11 ` Jayant R. Sonar
2012-02-23 12:33 ` Gerald Pfeifer
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=Pine.LNX.4.64.1110041546340.8834@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Jayant.Sonar@kpitcummins.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@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).