From: Yodel <yodel.eldar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb/alpha: Add target description support
Date: Mon, 26 May 2025 12:14:37 -0500 [thread overview]
Message-ID: <CAHhgW4XL1sor0qO7=_kstJjstSwMr4a+35pVyhd5pkMrwXh5vA@mail.gmail.com> (raw)
In-Reply-To: <8634crz6xu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]
On Mon, May 26, 2025 at 11:13 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Yodel Eldar <yodel.eldar@gmail.com>
> > Cc: Yodel Eldar <yodel.eldar@gmail.com>
> > Date: Mon, 26 May 2025 10:12:18 -0500
> >
> > This commit adds target description support for Alpha.
> >
> > The target description obviates the alpha_register_type and
> > alpha_register_name functions in alpha-tdep.c. Removal of
> > alpha_register_reggroup_p was considered but ultimately abandoned,
> > because the "info regs" command would no longer omit the zero, fpcr, and
> > unique registers from its output (they are neither vector nor float
> > types).
> >
> > Register types in the target description annex match the types that the
> > alpha_register_type function returned.
> >
> > The locally defined register_names array was moved out of
> > alpha_register_name and renamed to alpha_register_names as a static
> > global; calls to alpha_register_name have been replaced with direct
> > access of the array.
> >
> > The patch follows the code pattern outlined in the following GDB
> > Internals Wiki entry:
> >
> >
> https://sourceware.org/gdb/wiki/Internals%20Adding-Target-Described-Register-Support
> > ---
> > gdb/NEWS | 2 +
> > gdb/alpha-tdep.c | 87 ++++++++++++++++++++----------------
> > gdb/doc/gdb.texinfo | 42 ++++++++++++++++++
> > gdb/features/Makefile | 1 +
> > gdb/features/alpha-core.xml | 88 +++++++++++++++++++++++++++++++++++++
> > gdb/features/alpha.c | 84 +++++++++++++++++++++++++++++++++++
> > gdb/features/alpha.xml | 11 +++++
> > 7 files changed, 276 insertions(+), 39 deletions(-)
> > create mode 100644 gdb/features/alpha-core.xml
> > create mode 100644 gdb/features/alpha.c
> > create mode 100644 gdb/features/alpha.xml
>
> Thanks.
>
> > diff --git a/gdb/NEWS b/gdb/NEWS
> > index 2e48a00df5a..099c137a16f 100644
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -195,6 +195,8 @@ qXfer:threads:read
> > subsystem to be disabled at configure time, in the form of
> > --disable-gdb-compile.
> >
> > +* The Alpha target now supports target descriptions.
> > +
> > *** Changes in GDB 16
>
> This part is okay.
>
> > +The @samp{org.gnu.gdb.alpha.core} feature is required for Alpha
> targets. It
>
> ^^
> Two spaces between sentences, please.
>
> Thanks for pointing that out. It's corrected now.
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
>
[-- Attachment #2: Type: text/html, Size: 3719 bytes --]
next prev parent reply other threads:[~2025-05-26 17:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 15:12 [PATCH 0/2] gdb/alpha: Add target description support and fpcr flags Yodel Eldar
2025-05-26 15:12 ` [PATCH 1/2] gdb/alpha: Add target description support Yodel Eldar
2025-05-26 16:13 ` Eli Zaretskii
2025-05-26 17:14 ` Yodel [this message]
2025-06-03 18:49 ` Simon Marchi
2025-06-04 13:44 ` Yodel Eldar
2025-06-04 14:49 ` Maciej W. Rozycki
2025-06-04 17:29 ` Yodel Eldar
2025-06-12 19:29 ` Yodel Eldar
2025-06-12 20:30 ` Simon Marchi
2025-06-12 20:33 ` Simon Marchi
2025-06-12 22:07 ` Yodel Eldar
2025-06-13 14:34 ` Simon Marchi
2025-06-30 0:08 ` Yodel Eldar
2025-07-02 17:14 ` Simon Marchi
2025-07-02 18:51 ` Yodel Eldar
2025-07-02 18:53 ` Maciej W. Rozycki
2025-07-02 19:02 ` Simon Marchi
2025-07-02 19:21 ` Maciej W. Rozycki
2025-07-02 20:52 ` Yodel Eldar
2025-07-02 21:12 ` Maciej W. Rozycki
2025-07-03 16:49 ` Yodel Eldar
2025-07-03 16:02 ` Simon Marchi
2025-07-02 18:48 ` Maciej W. Rozycki
2025-05-26 15:12 ` [PATCH 2/2] gdb/alpha: Redefine fpcr with fpcr_flags type Yodel Eldar
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='CAHhgW4XL1sor0qO7=_kstJjstSwMr4a+35pVyhd5pkMrwXh5vA@mail.gmail.com' \
--to=yodel.eldar@gmail.com \
--cc=eliz@gnu.org \
--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