Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 08/25] Add "maint check xml-descriptions" to test builtin xml target descriptions
Date: Wed, 28 Jun 2017 16:13:00 -0000	[thread overview]
Message-ID: <f6bd6677-c418-4c6f-c714-a09b44e85d62@redhat.com> (raw)
In-Reply-To: <1497256916-4958-9-git-send-email-yao.qi@linaro.org>

On 06/12/2017 09:41 AM, Yao Qi wrote:

>  
> +@kindex maint check xml-descriptions
> +@item maint check xml-descriptions @var{dir}
> +Check the target descriptions created by @value{GDBN} equal to these
> +which are created from XML files in @var{dir}.

I'd suggest:

 Check that the target descriptions created dynamically by
 @value{GDBN} equal the descriptions created from XML files
 found in @var{dir}.

>    }
> +  bool operator!= (const tdesc_feature &other) const
> +  {

(Missing empty line just above the method.)

Nit, it's a bit more conventional to define operator==
instead, and then operator!= in terms of operator==,
like you had in other cases.  Can you do the same here?
It'd just mean swapping true/false in the body of this
function, I think.


> +
> +  bool operator!= (const target_desc &other) const
> +  {

Ditto.

>  
> +namespace selftests {
> +
> +static std::vector<std::pair<const char*, const target_desc *>> xml_tdesc;
> +
> +#if GDB_SELF_TEST
> +void
> +record_xml_tdesc (const char *xml_file, const struct target_desc *tdesc)
> +{
> +  xml_tdesc.emplace_back (xml_file, tdesc);
> +}
> +#endif
> +

Missing intro comments.

> +}
> +
> +/* Test these GDB builtin target descriptions equal to these which
> +   are generated by the corresponding xml files.  */

"these" here isn't specified (two times).  Can you name what
"these" are instead, avoiding indirection?  Maybe:

 Check that the target descriptions created dynamically by
 architecture-specific code, as registered in XML_TDESC,
 equal the descriptions created from XML files found in the
 specified directory.

> +
> +static void
> +maintenance_check_xml_descriptions (char *name, int from_tty)
> +{
> +  if (name == NULL)
> +    error (_("Missing dir name"));
> +
> +  std::string feature_dir (name);
> +  unsigned int failed = 0;

I'd suggest s/name/dir/ for a tiny bit more clarify.

> +
> +  for (auto const &e : selftests::xml_tdesc)
> +    {
> +      std::string tdesc_xml = (feature_dir + SLASH_STRING + e.first);
> +      const target_desc *tdesc
> +	= file_read_description_xml (tdesc_xml.data ());
> +
> +      if (tdesc == NULL || *tdesc != *e.second)
> +	failed++;
> +    }
> +  printf_filtered (_("%lu XML are tested, %d failed\n"),
> +		   (long) selftests::xml_tdesc.size (), failed);

s/are/were/.  Or better, I think:

  printf_filtered (_("Tested %lu XML files, %d failed\n"),
		   (long) selftests::xml_tdesc.size (), failed);

In the same spirit of "maint selftest"'s output.


> +
> +  add_cmd ("xml-descriptions", class_maintenance,
> +	   maintenance_check_xml_descriptions, _("\
> +Check the target descriptions.\n\
> +Takes a directory parameter."),

Can you expand this a little bit?

> +	   &maintenancechecklist);

Also, I tried the command manually, and noticed that it doesn't
support filename TAB completion.  You can fix that with:

  set_cmd_completer (c, filename_completer);

It'd be convenient too if it support tilde expansion:

 (gdb) maintenance check xml-descriptions ~/gdb/mygit/src/gdb/features
 warning: Could not open "~/gdb/mygit/src/gdb/features/i386/i386-linux.xml"
 warning: Could not open "~/gdb/mygit/src/gdb/features/i386/i386-mmx-linux.xml"
 warning: Could not open "~/gdb/mygit/src/gdb/features/i386/i386-avx-linux.xml"
 warning: Could not open "~/gdb/mygit/src/gdb/features/i386/i386-mpx-linux.xml"
 warning: Could not open "~/gdb/mygit/src/gdb/features/i386/i386-avx-mpx-linux.xml"
 warning: Could not open "~/gdb/mygit/src/gdb/features/i386/i386-avx-avx512-linux.xml"
 warning: Could not open "~/gdb/mygit/src/gdb/features/i386/i386-avx-mpx-avx512-pku-linux.xml"
 7 XML are tested, 7 failed
 (gdb) maintenance check xml-descriptions /home/pedro/gdb/mygit/src/gdb/features
 7 XML are tested, 0 failed

You can fix that by simply calling tilde_expand.


>  
> +#if GDB_SELF_TEST
> +namespace selftests {
> +
> +/* Record the target description TDESC generated by XML_FILE.  */

"record for what?" is a reasonable question that the comment
doesn't help with.  Maybe write something like this:

 Record that XML_FILE should generate a target description that
 equals TDESC, to be verified by the "maintenance check xml-descriptions"
 command.

> +
> +void record_xml_tdesc (const char *xml_file,
> +		       const struct target_desc *tdesc);
> +}
> +#endif
> +

Thanks,
Pedro Alves


  reply	other threads:[~2017-06-28 16:13 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12  8:42 [PATCH 00/25 V2] Make GDB builtin target descriptions more flexible Yao Qi
2017-06-12  8:42 ` [PATCH 22/25] Regenerate two regformats/i386/.dat files Yao Qi
2017-06-22 12:43   ` Yao Qi
2017-06-12  8:42 ` [PATCH 20/25] Centralize amd64-linux target descriptions Yao Qi
2017-06-12  8:42 ` [PATCH 07/25] Lazily and dynamically create i386-linux " Yao Qi
2017-06-20 11:01   ` Pedro Alves
2017-06-20 14:07     ` Yao Qi
2017-06-28 15:30       ` Pedro Alves
2017-06-12  8:42 ` [PATCH 15/25] [RFC] GDBserver unit test to i386_tdesc Yao Qi
2017-06-28 17:22   ` Pedro Alves
2017-06-29  9:27     ` Yao Qi
2017-06-12  8:42 ` [PATCH 14/25] [RFC] GDBserver self test Yao Qi
2017-06-28 17:09   ` Pedro Alves
2017-06-29  9:08     ` Yao Qi
2017-06-12  8:42 ` [PATCH 16/25] Dynamically composite xml in reply to GDB Yao Qi
2017-06-12  8:42 ` [PATCH 04/25] Centralize i386 linux target descriptions Yao Qi
2017-06-19 21:27   ` Simon Marchi
2017-06-12  8:42 ` [PATCH 09/25] Use target_desc fields expedite_regs and xmltarget ifndef IN_PROCESS_AGENT Yao Qi
2017-06-28 16:16   ` Pedro Alves
2017-06-28 17:42     ` Pedro Alves
2017-06-28 17:45       ` Pedro Alves
2017-06-29 11:45     ` Yao Qi
2017-06-12  8:42 ` [PATCH 01/25] Move initialize_tdesc_mips* calls from mips-linux-nat.c to mips-linux-tdep.c Yao Qi
2017-06-12 15:25   ` Maciej W. Rozycki
2017-06-13  8:07     ` Yao Qi
2017-06-12  8:42 ` [PATCH 02/25] Adjust the order of 32bit-linux.xml and 32bit-sse.xml in i386/i386-linux.xml Yao Qi
2017-06-19 20:22   ` Simon Marchi
2017-06-19 21:24     ` Pedro Alves
2017-06-19 21:48       ` Simon Marchi
2017-06-19 21:56         ` Pedro Alves
2017-06-20  9:20           ` Yao Qi
2017-06-20 10:12             ` Pedro Alves
2017-06-20 11:09               ` Yao Qi
2017-06-12  8:42 ` [PATCH 21/25] Lazily and dynamically create amd64-linux target descriptions Yao Qi
2017-06-12  8:42 ` [PATCH 12/25] [GDBserver] Centralize tdesc for i386-linux Yao Qi
2017-06-12  8:42 ` [PATCH 05/25] Use visitor pattern for "maint print c-tdesc" Yao Qi
2017-06-20 23:37   ` Simon Marchi
2017-06-12  8:42 ` [PATCH 25/25] Remove features/i386/amd64-*linux.c and features/i386/x32-*linux.c Yao Qi
2017-06-12  8:42 ` [PATCH 08/25] Add "maint check xml-descriptions" to test builtin xml target descriptions Yao Qi
2017-06-28 16:13   ` Pedro Alves [this message]
2017-06-12  8:42 ` [PATCH 24/25] [GDBserver] Use pre-generated amd64-linux tdesc as test Yao Qi
2017-06-12  8:42 ` [PATCH 17/25] Remove features/i386/i386-*linux.c Yao Qi
2017-06-12  8:42 ` [PATCH 23/25] [GDBserver] Convert amd64-linux target descriptions Yao Qi
2017-06-28 19:00   ` Pedro Alves
2017-06-12  8:42 ` [PATCH 18/25] [GDBserver] Use pre-generated tdesc as test Yao Qi
2017-06-12  8:42 ` [PATCH 19/25] GDBserver: remove srv_i386_linux_xmlfiles Yao Qi
2017-06-12  8:42 ` [PATCH 13/25] Dynamically create tdesc in GDBserver Yao Qi
2017-06-12  8:42 ` [PATCH 03/25] Class-fy tdesc_reg tdesc_type and tdesc_feature Yao Qi
2017-06-19 20:55   ` Simon Marchi
2017-06-19 21:30   ` Simon Marchi
2017-06-20 10:31     ` Yao Qi
2017-06-12  8:42 ` [PATCH 06/25] Generate c for feature instead of tdesc Yao Qi
2017-06-12 14:48   ` Eli Zaretskii
2017-06-13 12:07     ` Yao Qi
2017-06-13 14:49       ` Eli Zaretskii
2017-06-13 15:31         ` Yao Qi
2017-06-13 15:41           ` Eli Zaretskii
2017-06-14 16:21             ` Yao Qi
2017-06-14 16:32               ` Eli Zaretskii
2017-06-15 13:19                 ` Yao Qi
2017-06-15 14:45                   ` Eli Zaretskii
     [not found]   ` <d0c0b3b2-e585-acbb-d63e-6be6a6fe11a9@redhat.com>
     [not found]     ` <86mv90hyci.fsf@gmail.com>
2017-06-22 15:36       ` Pedro Alves
2017-06-22 15:58         ` Yao Qi
2017-06-26 21:38   ` Simon Marchi
2017-06-29 15:24     ` Yao Qi
2017-06-12  8:42 ` [PATCH 11/25] Use VEC for target_desc.reg_defs Yao Qi
2017-06-28 19:01   ` Pedro Alves
2017-06-29 11:05     ` Yao Qi
2017-06-29 11:31       ` Pedro Alves
2017-06-29 13:24         ` Yao Qi
2017-06-12  8:42 ` [PATCH 10/25] Adjust code generated by regformats/regdat.sh Yao Qi
     [not found]   ` <92ca03ca-e06d-09fc-7243-e52dd29edcef@redhat.com>
2017-06-21 14:28     ` Yao Qi
2017-06-19 19:59 ` [PATCH 00/25 V2] Make GDB builtin target descriptions more flexible Simon Marchi
2017-06-20 11:02   ` Yao Qi
2017-06-26 14:45   ` Tedeschi, Walfred
2017-06-27 13:49     ` Alan Hayward
2017-06-28  8:28       ` Yao Qi
2017-06-28  8:06     ` Yao Qi
2017-06-28 19:06 ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f6bd6677-c418-4c6f-c714-a09b44e85d62@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox