From: Simon Marchi <simon.marchi@polymtl.ca>
To: Stafford Horne <shorne@gmail.com>
Cc: GDB patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 3/3] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p
Date: Thu, 08 Jun 2017 20:52:00 -0000 [thread overview]
Message-ID: <59d8e3de4d7d586a39306ac65a1c7638@polymtl.ca> (raw)
In-Reply-To: <0c4f5b59a645a64535e7c8bb0f34b03df805f4e4.1496871270.git.shorne@gmail.com>
Hi Stafford,
On 2017-06-08 00:15, Stafford Horne wrote:
> @@ -1081,17 +1080,13 @@ tdesc_remote_register_number (struct gdbarch
> *gdbarch, int regno)
> }
>
> /* Check whether REGNUM is a member of REGGROUP. Registers from the
> - target description may be classified as general, float, or vector.
> - Unlike a gdbarch register_reggroup_p method, this function will
> - return -1 if it does not know; the caller should handle registers
> - with no specified group.
> -
> - Arbitrary strings (other than "general", "float", and "vector")
> - from the description are not used; they cause the register to be
> - displayed in "info all-registers" but excluded from "info
> - registers" et al. The names of containing features are also not
> - used. This might be extended to display registers in some more
> - useful groupings.
> + target description may be classified as general, float, vector or
> other
> + register groups registerd with reggroup_add(). Unlike a gdbarch
s/registerd/registered/
> @@ -1231,6 +1209,27 @@ tdesc_use_registers (struct gdbarch *gdbarch,
> void **slot = htab_find_slot (reg_hash, reg, INSERT);
>
> *slot = reg;
> + /* Add reggroup if its new. */
> + if (reg->group != NULL)
> + {
> + struct reggroup *group;
> + bool group_exists = false;
> +
> + for (group = reggroup_next (gdbarch, NULL);
> + group != NULL;
> + group = reggroup_next (gdbarch, group))
> + {
> + if (strcmp (reg->group, reggroup_name (group)) == 0)
> + {
> + group_exists = true;
> + break;
> + }
> + }
> +
> + if (!group_exists)
> + reggroup_add (gdbarch, reggroup_new (reg->group,
> + USER_REGGROUP));
Is the memory allocated by reggroup_new ever freed?
Simon
next prev parent reply other threads:[~2017-06-08 20:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 22:15 [PATCH 0/3] Support for arbitrary reggroups Stafford Horne
2017-06-07 22:16 ` [PATCH 3/3] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p Stafford Horne
2017-06-08 2:40 ` Eli Zaretskii
2017-06-08 5:01 ` Stafford Horne
2017-06-08 14:56 ` Eli Zaretskii
2017-06-08 20:52 ` Simon Marchi [this message]
2017-06-09 11:45 ` Stafford Horne
2017-06-09 19:59 ` Simon Marchi
2017-06-10 8:17 ` Stafford Horne
2017-06-13 11:17 ` Pedro Alves
2017-06-07 22:16 ` [PATCH 2/3] reggroups: Convert reggroups from post_init to pre_init Stafford Horne
2017-06-07 22:16 ` [PATCH 1/3] reggroups: Add test and docs for `info reg $reggroup` feature Stafford Horne
2017-06-08 2:38 ` Eli Zaretskii
2017-06-08 4:59 ` Stafford Horne
2017-06-08 20:31 ` Simon Marchi
2017-06-08 23:27 ` Stafford Horne
2017-06-09 6:20 ` Simon Marchi
2017-06-13 11:17 ` Pedro Alves
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=59d8e3de4d7d586a39306ac65a1c7638@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=shorne@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).