Re: contribute document?

[Ben Elliston <bje at au1 dot ibm dot com>]

> 1. Entering official release, need I contribute any document about
> our chip, such as architecture and ISA besides source code? or, what
> other resources should i offer?

You don't need to supply architecture or ISA documentation for
binutils ports.  The expectation is that this documentation can be
located by programmers if they want to use your port.  However, if
there are any user-visible features (for example, command line options
or pseudo-ops) that are specific to your port, then those need to be
included in the appropriate manual (eg. the gas manual).

> 2. If adding Binutils to official release, must gcc be added to
> official release too?  Dose gcc has the same way as Binutils to
> enter official release?

It is not a requirement that a GCC contribution be made at the same
time.  In fact, there have been binutils ports in the past for chips
that are too small or quirky to warrant a GCC port.  Users were happy
to just program them in assembly language.  In general, it does make
sense to contribute a GCC port around the same time, though.

Ben