From: Liu <proljc@gmail.com>
To: Xiangfu Liu <xiangfu@openmobilefree.net>
Cc: gcc@gcc.gnu.org
Subject: Re: I am work with lm32 and want to help with the lm32 target in gcc
Date: Thu, 01 Sep 2011 03:32:00 -0000 [thread overview]
Message-ID: <CAJBMM-vGi-bx2+NSd0P9KDT90bx2dAY7_ZfyB_xhG3b7+U9uyg@mail.gmail.com> (raw)
In-Reply-To: <4E5EF561.5090909@openmobilefree.net>
On Thu, Sep 1, 2011 at 11:00 AM, Xiangfu Liu <xiangfu@openmobilefree.net> wrote:
> Hi
>
> I am work with lm32 and want to help with the lm32 target in gcc.
> the device name is milkymist one. with FPGA software CPU core lm32.
>
> what is the first step I should do for help with lm32 target in gcc?
> I have read this http://gcc.gnu.org/contribute.html#legal
> I have to start with small contributions. should I do this legal stuff?
>
> thanks
>
ask for a assignment, sign it, send it back to FSF, and summit your patch.
--Liu
next prev parent reply other threads:[~2011-09-01 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 3:04 Xiangfu Liu
2011-09-01 3:32 ` Liu [this message]
2011-09-01 6:59 ` Xiangfu Liu
2011-09-04 8:00 ` Liu
2011-09-07 8:11 ` Xiangfu Liu
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=CAJBMM-vGi-bx2+NSd0P9KDT90bx2dAY7_ZfyB_xhG3b7+U9uyg@mail.gmail.com \
--to=proljc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=xiangfu@openmobilefree.net \
/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).