From: Michael Eager <eager@eagerm.com>
To: gcc-patches@gcc.gnu.org, GCC <gcc@gcc.gnu.org>
Subject: PING -- MicroBlaze target support patches
Date: Wed, 12 May 2010 19:53:00 -0000 [thread overview]
Message-ID: <4BEB0738.5060704@eagerm.com> (raw)
Could someone please review these patches?
Add support for Xilinx MicroBlaze processor:
http://gcc.gnu.org/ml/gcc-patches/2010-04/msg01903.html
http://gcc.gnu.org/ml/gcc-patches/2010-04/msg01905.html
http://gcc.gnu.org/ml/gcc-patches/2010-04/msg01908.html
http://gcc.gnu.org/ml/gcc-patches/2010-04/msg01907.html
http://gcc.gnu.org/ml/gcc-patches/2010-04/msg01906.html
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next reply other threads:[~2010-05-12 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 19:53 Michael Eager [this message]
2010-07-10 18:04 ` 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=4BEB0738.5060704@eagerm.com \
--to=eager@eagerm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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).