Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tankut Baris Aktemur <tankutbaris.aktemur@amd.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 02/16] gdb: convert address_class_type_flags_to_name to address_class_id_to_name
Date: Tue, 21 Jul 2026 12:03:35 -0600	[thread overview]
Message-ID: <87v7a8te2w.fsf@tromey.com> (raw)
In-Reply-To: <20260713-users-aktemur-type-instance-flags-v1-2-779cad0c85ec@amd.com> (Tankut Baris Aktemur's message of "Mon, 13 Jul 2026 09:00:01 -0500")

>>>>> Tankut Baris Aktemur <tankutbaris.aktemur@amd.com> writes:

> In type instance flags, two bits are allocated for encoding the
> address class.  Although defined like a bitmask, those two bits in
> fact represent an architecture-specific enum value.  As a step towards
> making this conceptual separation clear, refactor the gdbarch method
> 'address_class_type_flags_to_name'.  This method is used for returning
> the name for the address class id encoded in type instance flags.
> Make this clear by passing it the address class id, instead of the
> whole flags.

I have two small suggestions.

> +ft32_address_class_id_to_name (struct gdbarch *gdbarch,
> +			       unsigned int address_class)
>  {
> -  if (type_flags & TYPE_INSTANCE_FLAG_ADDRESS_CLASS_1)
> +  if (address_class == 1)

First, I just wanted to point this out explicitly: normally I'd ding
this for using a hard-coded constant; but in this case another function
in the same file does essentially the same, and anyway this is a tdep
file that hasn't perhaps had a non-refactoring patch since 2017.  So I
think this can slide.

>  Method(
>      type="const char *",
> -    name="address_class_type_flags_to_name",
> -    params=[("type_instance_flags", "type_flags")],
> +    name="address_class_id_to_name",
> +    params=[("unsigned int", "address_class")],
>      predicate=True,
>  )
 
I think this is a good opportunity to add a comment to describe the
method.

> -  else if ((space_flag & TYPE_INSTANCE_FLAG_ADDRESS_CLASS_ALL)
> -	   && gdbarch_address_class_type_flags_to_name_p (gdbarch))
> -    return gdbarch_address_class_type_flags_to_name (gdbarch, space_flag);
> +
> +  unsigned int aclass = TYPE_ADDRESS_CLASS_FROM_INSTANCE_FLAGS (space_flag);
> +
> +  if (aclass != 0
> +      && gdbarch_address_class_id_to_name_p (gdbarch))
> +    return gdbarch_address_class_id_to_name (gdbarch, aclass);

Here I think the code could check gdbarch_address_class_id_to_name_p and
then unconditionally call it with whatever the value happens to be --
IMO we can assume that the arch methods handle 0.

thanks,
Tom

  reply	other threads:[~2026-07-21 18:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 13:59 [PATCH 00/16] Rewrite type instance flags as a struct with bitfields Tankut Baris Aktemur
2026-07-13 14:00 ` [PATCH 01/16] gdb: use type instance macros to query const, volatile, restrict Tankut Baris Aktemur
2026-07-21 17:52   ` Tom Tromey
2026-07-13 14:00 ` [PATCH 02/16] gdb: convert address_class_type_flags_to_name to address_class_id_to_name Tankut Baris Aktemur
2026-07-21 18:03   ` Tom Tromey [this message]
2026-07-13 14:00 ` [PATCH 03/16] gdb: convert address_class_name_to_type_flags to address_class_name_to_id Tankut Baris Aktemur
2026-07-21 18:10   ` Tom Tromey
2026-07-13 14:00 ` [PATCH 04/16] gdb: convert address_class_type_flags to address_class_dwarf_to_id Tankut Baris Aktemur
2026-07-21 18:19   ` Tom Tromey
2026-07-13 14:00 ` [PATCH 05/16] gdb: inline address_space_{name, type_instance_flags}_to_{type_instance_flags, name} Tankut Baris Aktemur
2026-07-21 18:29   ` Tom Tromey
2026-07-22 10:29     ` Aktemur, Baris
2026-07-22 13:38       ` Tom Tromey
2026-07-13 14:00 ` [PATCH 06/16] gdb: split make_type_with_address_space Tankut Baris Aktemur
2026-07-21 18:49   ` Tom Tromey
2026-07-13 14:00 ` [PATCH 07/16] gdb: convert type instance flags to bitfields Tankut Baris Aktemur
2026-07-21 19:13   ` Tom Tromey
2026-07-22 10:29     ` Aktemur, Baris
2026-07-13 14:00 ` [PATCH 08/16] gdb: convert TYPE_NOTTEXT macro to type::is_nottext Tankut Baris Aktemur
2026-07-21 18:39   ` Tom Tromey
2026-07-13 14:00 ` [PATCH 09/16] gdb: convert TYPE_CONST macro to type::is_const Tankut Baris Aktemur
2026-07-21 18:40   ` Tom Tromey
2026-07-13 14:00 ` [PATCH 10/16] gdb: convert TYPE_VOLATILE macro to type::is_volatile Tankut Baris Aktemur
2026-07-13 14:00 ` [PATCH 11/16] gdb: convert TYPE_CODE_SPACE macro to type::is_code_space Tankut Baris Aktemur
2026-07-13 14:00 ` [PATCH 12/16] gdb: convert TYPE_DATA_SPACE macro to type::is_data_space Tankut Baris Aktemur
2026-07-13 14:00 ` [PATCH 13/16] gdb: convert TYPE_RESTRICT macro to type::is_restrict Tankut Baris Aktemur
2026-07-13 14:00 ` [PATCH 14/16] gdb: convert TYPE_ATOMIC macro to type::is_atomic Tankut Baris Aktemur
2026-07-13 14:00 ` [PATCH 15/16] gdb: convert TYPE_ADDRESS_CLASS macro to type::address_class Tankut Baris Aktemur
2026-07-13 14:00 ` [PATCH 16/16] gdb: remove unnecessary braces in recursive_dump_type Tankut Baris Aktemur
2026-07-21 18:45   ` 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=87v7a8te2w.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tankutbaris.aktemur@amd.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