From: Shahab Vahedi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>,
Shahab Vahedi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Shahab Vahedi <shahab.vahedi@gmail.com>,
Francois Bedard <Francois.Bedard@synopsys.com>
Subject: Re: [PATCH] arc: Write correct "eret" value during register collection
Date: Thu, 12 Nov 2020 15:46:27 +0000 [thread overview]
Message-ID: <6dfb04a3-ed08-6863-3593-5fd9e6e400d4@synopsys.com> (raw)
In-Reply-To: <871rgyfxqd.fsf@tromey.com>
Hi Tom,
On 11/12/20 3:36 PM, Tom Tromey wrote:
>>>>>> "Shahab" == Shahab Vahedi via Gdb-patches <gdb-patches@sourceware.org> writes:
> Shahab> /* Skip non-existing registers. */
> Shahab> - if ((arc_linux_core_reg_offsets[regnum] == ARC_OFFSET_NO_REGISTER))
> Shahab> + if (arc_linux_core_reg_offsets[regnum] == ARC_OFFSET_NO_REGISTER)
> Shahab> return;
> Shahab> + else
> Shahab> + offset = arc_linux_core_reg_offsets[ARC_ERET_REGNUM];
>
> I would drop the "else" here.
done.
>
> I didn't understand this patch. It unconditionally sets 'offset' to the
> offset of ARC_ERET_REGNUM. But surely that can't be correct?
> The assignment above does this, and so does...
>
> Shahab> if (regnum == gdbarch_pc_regnum (gdbarch))
> Shahab> - regnum = ARC_ERET_REGNUM;
> Shahab> - regcache->raw_collect (regnum, buf + arc_linux_core_reg_offsets[regnum]);
> Shahab> + offset = arc_linux_core_reg_offsets[ARC_ERET_REGNUM];
>
> ... this one.
You're absolutely correct. That was a snafu on my side. A second patch is submitted [1].
[1] [PATCH v2] arc: Write correct "eret" value during register collection
https://sourceware.org/pipermail/gdb-patches/2020-November/173212.html
Cheers,
Shahab
next prev parent reply other threads:[~2020-11-12 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 13:43 Shahab Vahedi via Gdb-patches
2020-11-12 14:36 ` Tom Tromey
2020-11-12 15:46 ` Shahab Vahedi via Gdb-patches [this message]
2020-11-12 15:42 ` [PATCH v2] " Shahab Vahedi via Gdb-patches
2020-11-12 15:43 ` Tom Tromey
2020-11-12 16:05 ` [PUSHED] " Shahab Vahedi via Gdb-patches
2020-12-04 10:57 ` [PUSHED gdb-10-branch] " Shahab Vahedi via Gdb-patches
2020-12-04 14:10 ` Joel Brobecker
2020-12-04 14:44 ` Shahab Vahedi via Gdb-patches
2020-12-04 14:53 ` Joel Brobecker
2020-12-04 15:38 ` Shahab Vahedi via Gdb-patches
2020-12-05 8:12 ` Joel Brobecker
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=6dfb04a3-ed08-6863-3593-5fd9e6e400d4@synopsys.com \
--to=gdb-patches@sourceware.org \
--cc=Francois.Bedard@synopsys.com \
--cc=Shahab.Vahedi@synopsys.com \
--cc=shahab.vahedi@gmail.com \
--cc=tom@tromey.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