From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 4/4] Poison bfd_boolean
Date: Sat, 07 Mar 2026 11:20:49 -0700 [thread overview]
Message-ID: <20260307-no-bfd-boolean-v1-4-186424bf8238@tromey.com> (raw)
In-Reply-To: <20260307-no-bfd-boolean-v1-0-186424bf8238@tromey.com>
BFD is moving away from bfd_boolean. This patch arranges for gdb to
do the same by having BFD poison the identifier so that no new uses
will creep in.
---
gdb/defs.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdb/defs.h b/gdb/defs.h
index b378449343d..de4f44e2458 100644
--- a/gdb/defs.h
+++ b/gdb/defs.h
@@ -32,6 +32,8 @@
#undef PACKAGE_TARNAME
#include <config.h>
+
+#define POISON_BFD_BOOLEAN
#include "bfd.h"
#include <sys/types.h>
--
2.49.0
next prev parent reply other threads:[~2026-03-07 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 18:20 [PATCH 0/4] Remove some bfd_boolean uses Tom Tromey
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 ` Tom Tromey [this message]
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-4-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