This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New target ported
- From: Geoff Keating <geoffk at geoffk dot org>
- To: Pablo Huerta <pablo dot huerta at alumnos dot unican dot es>
- Cc: gcc at gcc dot gnu dot org
- Date: 04 Dec 2003 12:24:27 -0800
- Subject: Re: New target ported
- References: <3FCF0A63.2030402@alumnos.unican.es>
Pablo Huerta <pablo.huerta@alumnos.unican.es> writes:
> I write to you, because our team have ported gcc 3.4 to a new platform
> (OpenRISC 1000), and we want to ask you if it will be possible to
> include it in the next official release.
Yes, it is possible, under some circumstances.
I'm assuming this is a completely new port, not a change to an
existing port. If that is the case, and if no changes to the generic
part of the compiler are necessary (changes to target-specific code in
the configure scripts don't count), then it can go into GCC 3.4.
Otherwise, it should probably go into GCC 3.5; but you'll want to
submit the patch as soon as possible, since it usually takes some time
to get everything correct.
To get it into GCC, you will need to submit it as one or more patches;
each change to the generic part of the compiler should be submitted
separately, plus another patch which is the actual port. Here's a
checklist which will help you avoid many possible mistakes, if you're
not used to submitting patches to GCC.
Checklist for submitting patches:
[ ] The message is sent to gcc-patches.
[ ] The message has a meaningful subject line.
[ ] The message contains a description of the change you want to make, and why.
[ ] The message says on what platform you tested the patch.
[ ] The patch is attached to the mail, and was generated with `diff -upN' or
`diff -cpN'.
[ ] The patch applies to FSF GCC.
[ ] The patch applies to a recent version of its branch.
[ ] If the patch is for a release branch, it is implementing functionality that
already exists in the mainline.
[ ] There is a ChangeLog entry before the patch, but not part of the patch
itself.
[ ] The ChangeLog entry is properly formatted.
[ ] The patch either fixes an existing testcase, or adds a new testcase.
[ ] If the patch adds or changes a feature, a documentation change is included.
[ ] If the patch adds or changes a hook, target macro, RTL type or tree type,
a documentation change is included.
[ ] You have assigned copyright to the FSF.
In addition, for a new port we ask that there be someone who is
willing to be the maintainer for the port.
--
- Geoffrey Keating <geoffk@geoffk.org>