public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/9] Remove char-based bitfield macros
Date: Fri, 27 Oct 2023 11:36:40 -0600	[thread overview]
Message-ID: <20231027-field-bits-v2-0-cbec64f2136a@adacore.com> (raw)

This series removes the char-based bitfield macros from gdbtypes.h,
moving the associated data into 'struct field'.  A few other minor
cleanups are done along the way.

Regression tested on x86-64 Fedora 36.

---
Changes in v2:
- Introduced accessibility enum per review
- Added two new simplification patches
- Link to v1: https://inbox.sourceware.org/gdb-patches/20230921-field-bits-v1-0-201285360900@adacore.com

---
Tom Tromey (9):
      Use .def file to stringify type codes
      Print field accessibility inline
      Remove byte vectors from cplus_struct_type
      Add field::is_public
      Remove some QUIT calls from need_access_label_p
      Remove some type field accessor macros
      Remove char-based bitfield macros
      Use enum accessibility in types and member functions
      Simplify C++ type-printing

 gdb/ada-valprint.c                       |   2 +-
 gdb/c-typeprint.c                        | 145 ++++++-------------------
 gdb/c-varobj.c                           |  39 ++-----
 gdb/compile/compile-cplus-types.c        |   7 +-
 gdb/cp-valprint.c                        |   4 +-
 gdb/dwarf2/read.c                        |  94 ++++------------
 gdb/gdbtypes.c                           | 181 +++++++------------------------
 gdb/gdbtypes.h                           | 162 ++++++++++++---------------
 gdb/p-typeprint.c                        |   6 +-
 gdb/p-valprint.c                         |   4 +-
 gdb/stabsread.c                          | 127 ++++++++--------------
 gdb/testsuite/gdb.base/ptype-offsets.exp |   6 -
 12 files changed, 228 insertions(+), 549 deletions(-)
---
base-commit: 2c1e03b4520e908aa1eb36ecda279047b17bab23
change-id: 20230921-field-bits-9b9f802eb42b

Best regards,
-- 
Tom Tromey <tromey@adacore.com>


             reply	other threads:[~2023-10-27 17:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 17:36 Tom Tromey [this message]
2023-10-27 17:36 ` [PATCH v2 1/9] Use .def file to stringify type codes Tom Tromey
2023-11-03  4:07   ` Simon Marchi
2023-11-03 15:52     ` Tom Tromey
2023-10-27 17:36 ` [PATCH v2 2/9] Print field accessibility inline Tom Tromey
2023-11-03  4:10   ` Simon Marchi
2023-11-03 15:53     ` Tom Tromey
2023-10-27 17:36 ` [PATCH v2 3/9] Remove byte vectors from cplus_struct_type Tom Tromey
2023-11-03  4:22   ` Simon Marchi
2023-11-03 16:07     ` Tom Tromey
2023-10-27 17:36 ` [PATCH v2 4/9] Add field::is_public Tom Tromey
2023-10-27 17:36 ` [PATCH v2 5/9] Remove some QUIT calls from need_access_label_p Tom Tromey
2023-10-27 17:36 ` [PATCH v2 6/9] Remove some type field accessor macros Tom Tromey
2023-10-27 17:36 ` [PATCH v2 7/9] Remove char-based bitfield macros Tom Tromey
2023-10-27 17:36 ` [PATCH v2 8/9] Use enum accessibility in types and member functions Tom Tromey
2023-10-27 17:36 ` [PATCH v2 9/9] Simplify C++ type-printing Tom Tromey
2023-11-02 16:54 ` [PATCH v2 0/9] Remove char-based bitfield macros Keith Seitz
2023-11-03  4:23   ` Simon Marchi

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=20231027-field-bits-v2-0-cbec64f2136a@adacore.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).