This is the mail archive of the
mailing list for the binutils project.
Re: [PATCH 2/5] New target port: Andes 'nds32'. (opcode)
- From: Kuan-Lin Chen <kuanlinchentw at gmail dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>, binutils at sourceware dot org
- Date: Fri, 12 Jul 2013 13:59:29 +0800
- Subject: Re: [PATCH 2/5] New target port: Andes 'nds32'. (opcode)
- References: <CAJr6u0i7FwrYW9V7KB93UvOibTQQb5pZ6ZgNB1jVFvhc8mBJwg at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1307091628540 dot 23421 at digraph dot polyomino dot org dot uk>
2013/7/10 Joseph S. Myers <firstname.lastname@example.org>:
> Where is the source code for this patch? That is, the CGEN CPU
> description (for addition to the cpu/ directory). Almost all this patch
> appears to be generated files (which aren't needed in the diff; you just
> need to give instructions for the person committing the patch to generate
> them with CGEN).
Because we modified some general parts of CGEN, I did not send the source
code in this patch. The modification for two reason:
1. Add instruction print handler to disassemble more information for
2. In our target design, there are big and little endian for data but always big
endian for instruction. In original CGEN, it does not support
and instruction endian, so we modified it.
We plan to write this part (opcode/) by ourselves not generating by
CGEN in the feature.
So, do I have to send all the modification of CGEN?
Thanks for your comment.