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 v2 1/2] Use boolean constants in ft32-tdep.c
Date: Mon, 09 Mar 2026 07:56:26 -0600	[thread overview]
Message-ID: <20260309-no-bfd-boolean-v2-1-640b6b81c96d@tromey.com> (raw)
In-Reply-To: <20260309-no-bfd-boolean-v2-0-640b6b81c96d@tromey.com>

A couple of spots in ft32-tdep.c are using integer literals where
booleans are more appropriate.
---
 gdb/ft32-tdep.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/ft32-tdep.c b/gdb/ft32-tdep.c
index fc796f44ae1..5a1f3315c7f 100644
--- a/gdb/ft32-tdep.c
+++ b/gdb/ft32-tdep.c
@@ -206,7 +206,7 @@ ft32_analyze_prologue (CORE_ADDR start_addr, CORE_ADDR end_addr,
   if (start_addr >= end_addr)
     return end_addr;
 
-  cache->established = 0;
+  cache->established = false;
   for (next_addr = start_addr; next_addr < end_addr; next_addr += isize)
     {
       inst = ft32_fetch_instruction (next_addr, &isize, byte_order);
@@ -251,7 +251,7 @@ ft32_analyze_prologue (CORE_ADDR start_addr, CORE_ADDR end_addr,
       inst = ft32_fetch_instruction (next_addr, &isize, byte_order);
       if (FT32_IS_LINK (inst))
 	{
-	  cache->established = 1;
+	  cache->established = true;
 	  for (regnum = FT32_R0_REGNUM; regnum < FT32_PC_REGNUM; regnum++)
 	    {
 	      if (cache->saved_regs[regnum] != REG_UNAVAIL)

-- 
2.49.0


  reply	other threads:[~2026-03-09 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 13:56 [PATCH v2 0/2] Update some spots that were using bfd_boolean Tom Tromey
2026-03-09 13:56 ` Tom Tromey [this message]
2026-03-09 13:56 ` [PATCH v2 2/2] Use store_unsigned_integer in findcmd.c Tom Tromey
2026-03-09 16:04 ` [PATCH v2 0/2] Update some spots that were using bfd_boolean Simon Marchi
2026-03-09 16:59 ` Andrew Burgess

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=20260309-no-bfd-boolean-v2-1-640b6b81c96d@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