Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] typeprint.h: reorder struct declaration
Date: Thu, 31 Dec 2020 15:51:12 +0000	[thread overview]
Message-ID: <20201231155112.GS2945@embecosm.com> (raw)
In-Reply-To: <d1bd0dd6-4d83-5dc2-2bbc-e0b1e5db4b2e@lancelotsix.com>

* Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org> [2020-12-31 13:01:26 +0000]:

> Hi
> 
> On 31/12/2020 12:53, Lancelot SIX via Gdb-patches wrote:
> > Move the declaration of struct type_print_raw_options before struct
> > print_offset_data to ease upcoming changes. This is a helper commit
> > intended to make it easier to build a print_offset_data object from
> > configurations given by a type_print_raw_options.
> > 
> > gdb/ChangeLog:
> > 
> > 	* typeprint.h (struct type_print_options): move before
> > 	  print_offsetdata
> 
> Just realized I had formatting issues here. I’ll change that ASAP, with
> other elements that might come with reviews.

Good spot :) Just to ensure we're in sync, there's a white space issue
on line #2, and you should capitalise 'Move', and end with a full stop.

> 
> When doing such modification, do I re-send the entire patches series or just
> the one affected? (I am not yet familiar with working with mailing-list
> based workflows).

When it is just one patch changing independent of the others, and if
the changes are not huge (so minor clean ups), I would normally just
reply to the original patch with a new version.

When I've revised multiple patches, or if I make large changes to a
patch, I'll post the whole series again with a v2, v3, etc added.

Otherwise, this first patch looks fine.

Thanks,
Andrew

> 
> BR
> 
> Lancelot
> 
> > ---
> >   gdb/typeprint.h | 60 ++++++++++++++++++++++++-------------------------
> >   1 file changed, 30 insertions(+), 30 deletions(-)
> > 
> > diff --git a/gdb/typeprint.h b/gdb/typeprint.h
> > index d595cbe208..b75fa4d9f2 100644
> > --- a/gdb/typeprint.h
> > +++ b/gdb/typeprint.h
> > @@ -26,6 +26,36 @@ struct ui_file;
> >   struct typedef_hash_table;
> >   struct ext_lang_type_printers;
> > +struct type_print_options
> > +{
> > +  /* True means that no special printing flags should apply.  */
> > +  unsigned int raw : 1;
> > +
> > +  /* True means print methods in a class.  */
> > +  unsigned int print_methods : 1;
> > +
> > +  /* True means print typedefs in a class.  */
> > +  unsigned int print_typedefs : 1;
> > +
> > +  /* True means to print offsets, a la 'pahole'.  */
> > +  unsigned int print_offsets : 1;
> > +
> > +  /* The number of nested type definitions to print.  -1 == all.  */
> > +  int print_nested_type_limit;
> > +
> > +  /* If not NULL, a local typedef hash table used when printing a
> > +     type.  */
> > +  typedef_hash_table *local_typedefs;
> > +
> > +  /* If not NULL, a global typedef hash table used when printing a
> > +     type.  */
> > +  typedef_hash_table *global_typedefs;
> > +
> > +  /* The list of type printers associated with the global typedef
> > +     table.  This is intentionally opaque.  */
> > +  struct ext_lang_type_printers *global_printers;
> > +};
> > +
> >   struct print_offset_data
> >   {
> >     /* The offset to be applied to bitpos when PRINT_OFFSETS is true.
> > @@ -73,36 +103,6 @@ struct print_offset_data
> >   			 const char *for_what);
> >   };
> > -struct type_print_options
> > -{
> > -  /* True means that no special printing flags should apply.  */
> > -  unsigned int raw : 1;
> > -
> > -  /* True means print methods in a class.  */
> > -  unsigned int print_methods : 1;
> > -
> > -  /* True means print typedefs in a class.  */
> > -  unsigned int print_typedefs : 1;
> > -
> > -  /* True means to print offsets, a la 'pahole'.  */
> > -  unsigned int print_offsets : 1;
> > -
> > -  /* The number of nested type definitions to print.  -1 == all.  */
> > -  int print_nested_type_limit;
> > -
> > -  /* If not NULL, a local typedef hash table used when printing a
> > -     type.  */
> > -  typedef_hash_table *local_typedefs;
> > -
> > -  /* If not NULL, a global typedef hash table used when printing a
> > -     type.  */
> > -  typedef_hash_table *global_typedefs;
> > -
> > -  /* The list of type printers associated with the global typedef
> > -     table.  This is intentionally opaque.  */
> > -  struct ext_lang_type_printers *global_printers;
> > -};
> > -
> >   extern const struct type_print_options type_print_raw_options;
> >   /* A hash table holding typedef_field objects.  This is more

  reply	other threads:[~2020-12-31 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 12:53 [PATCH 0/2][PR cli/22640] Have ptype support hex display of offsets and sizes Lancelot SIX via Gdb-patches
2020-12-31 12:53 ` [PATCH 1/2] typeprint.h: reorder struct declaration Lancelot SIX via Gdb-patches
2020-12-31 13:01   ` Lancelot SIX via Gdb-patches
2020-12-31 15:51     ` Andrew Burgess [this message]
2020-12-31 12:53 ` [PATCH 2/2] ptype: add option to use hexadecimal notation Lancelot SIX via Gdb-patches
2021-04-13 23:18   ` John Baldwin
2021-04-14  0:08     ` Paul Koning via Gdb-patches
2021-04-14 22:45       ` Lancelot SIX via Gdb-patches
2021-04-15  0:08         ` Paul Koning via Gdb-patches
2021-04-14 22:33     ` Lancelot SIX via Gdb-patches

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=20201231155112.GS2945@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.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