This is the mail archive of the
mailing list for the binutils project.
Re: PING: Re: [PATCHv2 0/2] Add initial arc nps400 support
- From: Andrew Burgess <andrew dot burgess at embecosm dot com>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: binutils at sourceware dot org, noamca at mellanox dot com, Claudiu dot Zissulescu at synopsys dot com, Cupertino dot Miranda at synopsys dot com
- Date: Tue, 15 Mar 2016 11:37:40 +0000
- Subject: Re: PING: Re: [PATCHv2 0/2] Add initial arc nps400 support
- Authentication-results: sourceware.org; auth=none
- References: <20160302193711 dot GB9275 at embecosm dot com> <cover dot 1456947552 dot git dot andrew dot burgess at embecosm dot com> <20160311201339 dot GB14100 at embecosm dot com> <56E7EEA4 dot 8010709 at redhat dot com>
* Nick Clifton <email@example.com> [2016-03-15 11:14:44 +0000]:
> Hi Andrew,
> > PING! I've had some great feedback from Claudiu, but I'm still hoping
> > for a global maintainer to cast an eye over this too please.
> Oops - sorry - dropped the ball on this one.
No problem. Thanks for the review.
> The patches (1 and 2) both look fine to me, apart from one very small issue:
> The new assembler test control files (gas/testsuite/gas/arc/nps400-0.d and
> gas/testsuite/gas/arc/nps400-1.d) both restrict the test to:
> #target: arc*-mellanox-*
> What is "mellanox" and why is it included in the target string ? The name
> is not present in the gas/configure.tgt or bfd/config.bfd files, so I am
> assuming that it is a manufacturer name and not an OS name. If so then its
> presence in these tests will stop them from being run with toolchains
> configured with, for example, --target=arc-elf. (This matters to me, since
> that is one of the configurations I use in my daily regression
Patch #2 adds this name to the opcodes/configure script. I
deliberately tried to minimise the number of configure scripts I
The mellanox nps400 core is an ARC700 with a set of vendor extension
instructions added into the gap that is left in the ARC700
architecture specifically for such instructions.
So, at the moment, when we configure with arc*-mellanox-* in the
opcodes directory we build the standard arc opcodes library, but
include an additional set of instructions that sit in the gap.
Everything else (right now) bfd/gas/etc is unchanged.
In the future this might not be the case, for bfd/ld I do have some
small patches to submit, but they can wait for another day. I'm
hopeful that gas might not require any mellanox specific changes
With this new knowledge, are the patches still OK?