This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: OpenRISC port ready for inclusion

Hi Olaf,

What we have is a repo tracking upstream,a diff against
binutils-2.24.1 and all contributors to the OpenRISC-specific parts
are ready to sign over their respective parts to FSF... so how do we

Thanks very much for considering contributing this work. The first step is to make sure that all of the copyright holders for the work have FSF copyright assignments in place. (I am attaching the form necessary to apply for this assignment in case you need it).

Next, send the patches to the binutils list for review. It helps if you can break the patches down by sub-directory, ie bfd, opcodes, gas, ld etc. It also helps if the code has been written following the GNU Coding Standards:

The patches should made against the current development sources and should compile without any problems on both 32-bit and 64-bit hosts. There is no need to submit patches against generate files (eg configure, bfd-in2.h, etc). It is helpful however if you can include ChangeLog entries describing the patches, although these are best presented as plain text rather than context diffs.

It is also helpful if you can include some target specific testcases for both the assembler and the linker, to verify that the port is working. You should also build a toolchain configured with "--enable-targets=all", just to make sure that your changes do not affect any other targets.

You should also consider who will be maintaining the port. If the port is not going to have a maintainer who will help to look after it then it is unlikely to be accepted in the first place. (Unmaintained code tends to bit-rot and cause complications for other targets).


Attachment: request-assign.future
Description: Text document

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]