Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/4] Remove some bfd_boolean uses
Date: Sat, 07 Mar 2026 11:20:45 -0700	[thread overview]
Message-ID: <20260307-no-bfd-boolean-v1-0-186424bf8238@tromey.com> (raw)

I saw some recent commits removing uses of bfd_boolean from the tree.
This series removes the remaining uses from gdb as well, and then
arranges to poison the identifier using the BFD-supplied approach.

Signed-off-by: Tom Tromey <tom@tromey.com>
---
Tom Tromey (4):
      Use bool, not bfd_boolean
      Don't use BFD TRUE/FALSE constants
      Drop use of bfd_boolean from findcmd.c
      Poison bfd_boolean

 gdb/arc-linux-tdep.c              |  6 +++---
 gdb/compile/compile-object-load.c |  4 ++--
 gdb/defs.h                        |  2 ++
 gdb/elfread.c                     |  2 +-
 gdb/findcmd.c                     | 33 +++++++++++++--------------------
 gdb/ft32-tdep.c                   |  6 +++---
 gdb/machoread.c                   |  4 ++--
 7 files changed, 26 insertions(+), 31 deletions(-)
---
base-commit: a00fddb175ff5cb9edef18beedfba38fc6fc6017
change-id: 20260307-no-bfd-boolean-1c8cbdbf2849

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


             reply	other threads:[~2026-03-07 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 18:20 Tom Tromey [this message]
2026-03-07 18:20 ` [PATCH 1/4] Use bool, not bfd_boolean Tom Tromey
2026-03-07 18:20 ` [PATCH 2/4] Don't use BFD TRUE/FALSE constants Tom Tromey
2026-03-07 18:20 ` [PATCH 3/4] Drop use of bfd_boolean from findcmd.c Tom Tromey
2026-08-07 12:54   ` Guinevere Larsen
2026-03-07 18:20 ` [PATCH 4/4] Poison bfd_boolean Tom Tromey
2026-08-07 12:55 ` [PATCH 0/4] Remove some bfd_boolean uses Guinevere Larsen
2026-08-21 16:42   ` Tom Tromey

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=20260307-no-bfd-boolean-v1-0-186424bf8238@tromey.com \
    --to=tom@tromey.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