From: Tom Tromey <tom@tromey.com>
To: Alexey Lapshin via Gdb-patches <gdb-patches@sourceware.org>
Cc: Alexey Lapshin <alexey.lapshin@espressif.com>,
Alexey Gerenkov <alexey.gerenkov@espressif.com>,
Anton Maklakov <anton.maklakov@espressif.com>,
Ivan Grokhotkov <ivan@espressif.com>,
"jcmvbkbc@gmail.com" <jcmvbkbc@gmail.com>
Subject: Re: [PATCH] gdb: xtensa: don't supply registers if they are not present
Date: Wed, 09 Nov 2022 13:12:02 -0700 [thread overview]
Message-ID: <87iljn28h9.fsf@tromey.com> (raw)
In-Reply-To: <0d57c0fea0de71984c048e33763582a4acbf51d0.camel@espressif.com> (Alexey Lapshin via Gdb-patches's message of "Wed, 9 Nov 2022 19:15:41 +0000")
>>>>> "Alexey" == Alexey Lapshin via Gdb-patches <gdb-patches@sourceware.org> writes:
Alexey> @@ -813,6 +813,12 @@ xtensa_register_reggroup_p (struct gdbarch
Alexey> *gdbarch,
Alexey> in the general-purpose register set REGSET to register cache
Alexey> REGCACHE. If REGNUM is -1 do this for all registers in REGSET. */
Alexey> +static inline bool
Alexey> +is_reg_raw_supplied (int check_regnum, int regnum)
Alexey> +{
This seems to insert the new function between a comment and the function
that comment describes.
Tom
prev parent reply other threads:[~2022-11-09 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 19:15 Alexey Lapshin
2022-11-09 20:12 ` Tom Tromey [this message]
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=87iljn28h9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=alexey.gerenkov@espressif.com \
--cc=alexey.lapshin@espressif.com \
--cc=anton.maklakov@espressif.com \
--cc=gdb-patches@sourceware.org \
--cc=ivan@espressif.com \
--cc=jcmvbkbc@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).