This is the mail archive of the
mailing list for the binutils project.
Re: [PATCH] GAS: Add ECOFF `.aent' pseudo-op support
- From: Nick Clifton <nickc at redhat dot com>
- To: "Maciej W. Rozycki" <macro at imgtec dot com>, binutils at sourceware dot org
- Date: Fri, 17 Feb 2017 15:07:36 +0000
- Subject: Re: [PATCH] GAS: Add ECOFF `.aent' pseudo-op support
- Authentication-results: sourceware.org; auth=none
- References: <alpine.DEB.email@example.com>
> Assembly language documentation available describes the pseudo-op
> respectively as follows:
> .aent name, symno Sets an alternate entry point for the current
> procedure. Use this information when you want
> to generate information for the debugger. It must
> appear inside an .ent/.end pair."
> .aent name [,symno]
> Sets an alternate entry point for the current procedure. Use this
> information when you want to generate information for the debugger.
> This directive must appear between a pair of .ent and .end directives.
> (The optional symno is for compiler use only. It refers to a dense
> number in a .T file (symbol table).)"
Should this documentation be added to gas/doc/as.texinfo ? Or failing that
maybe names of the pseudo ops could be added along with the URLs in  and  ?
> * ecoff.c (ecoff_directive_ent, add_procedure): Handle `.aent'.
> * config/obj-ecoff.c (obj_pseudo_table): Add "aent" entry.
> * config/obj-elf.c (ecoff_debug_pseudo_table): Likewise.
> * testsuite/gas/mips/aent-2.d: New test.
> * testsuite/gas/mips/aent-mdebug.d: New test.
> * testsuite/gas/mips/aent-mdebug-2.d: New test.
> * testsuite/gas/mips/mips.exp: Run the new tests.
Approved - please apply.
Is this feature worth an entry in the gas/NEWS file ? I am not an aficionado of
the ECOFF format, so I am not sure of the significance of the feat