This is the mail archive of the
mailing list for the GCC project.
Re: How can I add S+core backend code into GCC package
- From: Mark Mitchell <mark at codesourcery dot com>
- To: liqin at sunnorth dot com dot cn
- Cc: David Edelsohn <dje at watson dot ibm dot com>, gcc-patches at gcc dot gnu dot org, richard at codesourcery dot com, bg19202 at hotmail dot com
- Date: Sun, 08 Oct 2006 21:38:32 -0700
- Subject: Re: How can I add S+core backend code into GCC package
- References: <OFEBFE8074.A5F09C45-ON48257201.0017857B-48257201.00186E0D@sunnorth.com.cn>
> I still have some questions below:
> 1: How can I check our code in, maybe someone need give me a
> username/passwprd for svn library.
Please follow the instructions here:
You may use my name as the person who approved your request for access.
> 2: How can I update the gcc/configure and gcc/config.gcc file.
The config.gcc file should not require any special steps. However, the
gcc/configure script should be regenerated with the same version of
autoconf used at present, which is autoconf 2.59.
> 3: If I want check score backend code into 4.1.x branch, what should i do?
In general, we don't put new features (including new ports) on release
branches. I might make an exception, since your port touches almost
nothing outside of the port directory, but I would want some input from
other developers. If you want to do this, the first step would
obviously be to do the actual backport, and test it, to make sure it
works. Even if you can't put it on the 4.1.x branch, you could put it
on a subbranch.
(650) 331-3385 x713