This is the mail archive of the
mailing list for the binutils project.
Re: bfd target vector rationalisation
- From: Alan Modra <amodra at gmail dot com>
- To: Tristan Gingold <gingold at adacore dot com>
- Cc: binutils at sourceware dot org
- Date: Fri, 2 May 2014 20:14:05 +0930
- Subject: Re: bfd target vector rationalisation
- Authentication-results: sourceware.org; auth=none
- References: <20140430143503 dot GE16139 at bubble dot grove dot modra dot org> <BDF250AD-2E76-42C3-9A65-72D5DF8B3C0E at adacore dot com>
On Wed, Apr 30, 2014 at 04:42:48PM +0200, Tristan Gingold wrote:
> On 30 Apr 2014, at 16:35, Alan Modra <firstname.lastname@example.org> wrote:
> > This renames the bfd targets to <cpu>_<format>_<other>_<endian>_vec.
> > So for example, bfd_elf32_ntradlittlemips_vec becomes
> > mips_elf32_ntrad_le_vec and hp300bsd_vec becomes m68k_aout_hp300bsd_vec.
> Shouldn't this convention be documented (for example in targets.c) ?
Good point. I added this to the comment:
Try to keep it in order when adding new targets, and
use a name of the form <cpu>_<format>_<other>_<endian>_vec.
Note that sorting is done as if _<endian>_vec wasn't present.
Australia Development Lab, IBM