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: [PATCHv3 0/7] Add initial arc nps400 support

* Pedro Alves <> [2016-03-17 16:15:07 +0000]:

> On 03/15/2016 11:01 PM, Andrew Burgess wrote:
> > Here's a rewrite that removes the need to use the vendor string in
> > order change the behaviour of binutils[1].
> >
> > [1] I still don't understand why that's a bad thing though....
> In an --enable-targets=all world, you need to be able to select
> any supported target at run time.  Thus, IIUC, in the vendor string
> version, an --enable-targets=all build wouldn't include
> nps400 support, unless you also specified the primary
> target as --target=arm-mellanox.
> Nowadays, the vendor/manufacturer string is meant to be free
> form, and set by whoever builds the tools to whatever they
> like, for branding purposes and $PATH coexistence.

Thanks for the explanation.  And remembering that I've already updated
the patch, so I ask only out of interest...

... I still think that allowing the vendor string to control some
defaults would be nice.  So in my case it would be great if the
default architecture for an arc-mellanox toolchain was nps400, from a
user PoV that seems like it would be a nicer experience .... maybe.

Anyway, thanks again for the explanation,

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