Re: How to create test suite .d files?

[Patrick Conlon <cptjustice at gmail dot com>]

Thank you for the pointer to the right places to read.  I made one by hand
from the objdump -dw output which I'll submit along with the patch and test
assembly.  I thought there would be a script or whatnot that the output of
objdump could be fed into.  Doing it by hand isn't hard, though.

Thank you again,
Patrick Conlon

On Mon, Aug 6, 2018 at 10:30 AM Maciej W. Rozycki <macro@linux-mips.org>
wrote:

> On Mon, 6 Aug 2018, Patrick Conlon wrote:
>
> > Thinking to make maintainers' lives easier, I submitted some test
> assembly
> > along with a patch.  What I haven't been able to figure out is how to
> > create the .d files in the test suite nor whatever documentation there is
> > regarding them.  While they is obviously a variation of objdump, when I
> run
> > it with the command line flags listed in other .d files, I don't get the
> > same output.
>
>  See the inline documentation at individual `run_dump_test' procedures in
> `binutils/testsuite/lib/utils-lib.exp', `gas/testsuite/lib/gas-defs.exp'
> and `ld/testsuite/lib/ld-lib.exp', respectively.  Please note the slight
> differences in options according to the tool being tested, and also that
> the dumps need not necessarily be from `objdump', as `readelf' and `nm'
> are also commonly used for output examination.
>
>  HTH,
>
>   Maciej
>