From: Gopi Kumar Bulusu <gopi@sankhya.com>
To: Michael Eager <eager@eagercon.com>
Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [pushed] MicroBlaze: Update software breakpoint machine code as per MicroBlaze ISA
Date: Wed, 10 Sep 2025 10:44:02 +0530 [thread overview]
Message-ID: <CAL1P33x=wanLORS1f5tdHYYWL0Bf6_HXDRDXj3VDY6pKbCNWZA@mail.gmail.com> (raw)
In-Reply-To: <CAL1P33xHrd_qDP9VR49JUaCJDzmz4TiXWn-JzTC0BuQP3dPRNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2860 bytes --]
On Tue, Sep 9, 2025 at 10:11 PM Gopi Kumar Bulusu <gopi@sankhya.com> wrote:
>
>
> On Tue, Sep 9, 2025, 9:59 PM Michael Eager <eager@eagercon.com> wrote:
>
>> On 9/9/25 9:05 AM, Gopi Kumar Bulusu wrote:
>> >
>> >
>> > On Tue, Sep 9, 2025, 9:04 PM Simon Marchi <simark@simark.ca
>> > <mailto:simark@simark.ca>> wrote:
>> >
>> > On 9/9/25 11:31 AM, Simon Marchi wrote:
>> > > On 9/9/25 3:16 AM, Gopi Kumar Bulusu wrote:
>> > >> namaskaaram,
>> > >>
>> > >> The macro MICROBLAZE_BREAKPOINT is set to an instruction opcode
>> > that does not meet the criteria for software breakpoint instruction
>> > as set forth in the AMD MicroBlaze ISA. This patch addresses the
>> > problem.
>> > >>
>> > >> This simple patch concludes a series of patches that add AMD
>> > MicroBlaze gdbserver target support for GNU/Linux.
>> > >>
>> > >> Updated NEWS to include MicroBlaze gdbserver target.
>> > >>
>> > >> Build/Test - tested by building microblazeel-linux-gdb and
>> > verifying that software breakpoint works
>> > >> using gdbserver as target.
>> > >>
>> > >> dhanyavaadaaha
>> > >> gopi
>> > >>
>> > >
>> > > Can you explain how the NEWS entry you add relates to the code
>> > change?
>> > >
>> > > Simon
>> >
>> > It sounds like it is related to this patch, merged back in March:
>> >
>> > https://sourceware.org/git/?p=binutils-
>> > gdb.git;a=commit;h=a93f60043a26e0b8b0ea71a63201b9352ce52a6f
>> > <https://sourceware.org/git/?p=binutils-
>> > gdb.git;a=commit;h=a93f60043a26e0b8b0ea71a63201b9352ce52a6f>
>> >
>> > If so, then the NEWS entry should be in the "Changes in GDB 17"
>> section,
>> > and cherry-picked to the gdb-17-branch branch (and it should not be
>> > added
>> > in this particular patch).
>> >
>> >
>> > All the patches in a series of changes ( bfd, gdb, gdbserver) are
>> needed
>> > for breakpoint to work from gdb for gdbserver target.
>> >
>> > After a discussion at the beginning of this work (over a year ago) - I
>> > followed the path of submitting patches as smaller logical units.
>>
>> Neither of these points appear to be relevant to this patch.
>>
>> > I can merge the last 2 (including this) MicroBlaze patches to the
>> > gdb-17 branch as well.
>>
>> Let's work on one patch at a time and not confuse matters by referring
>> to other unrelated patches.
>>
>> Please split this patch into two. One change to NEWS, the other
>> changing the breakpoint op code.
>>
>
> Ok, I will do so.
>
pushed 2dda928eb2f2764adaed515f513227cea8d16564
(microblaze-tdep.h)
pushed c8af46a9cc214f8ef70d189ead632419d5889c2f
(NEWS update)
dhanyavaadaaha
gopi
> dhanyavaadaaha
> gopi
>
>>
>>
[-- Attachment #2: Type: text/html, Size: 5200 bytes --]
next prev parent reply other threads:[~2025-09-10 5:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 7:16 [PATCH] " Gopi Kumar Bulusu
2025-09-09 11:56 ` Michael Eager
2025-09-09 12:23 ` Gopi Kumar Bulusu
2025-09-09 13:35 ` Michael Eager
2025-09-09 15:31 ` Simon Marchi
2025-09-09 15:34 ` Simon Marchi
2025-09-09 16:05 ` Gopi Kumar Bulusu
2025-09-09 16:22 ` Simon Marchi
2025-09-09 16:39 ` Gopi Kumar Bulusu
2025-09-09 16:29 ` Michael Eager
2025-09-09 16:41 ` Gopi Kumar Bulusu
2025-09-10 5:14 ` Gopi Kumar Bulusu [this message]
2025-09-10 13:27 ` [pushed] " Michael Eager
2025-09-10 15:09 ` Simon Marchi
2025-09-09 15:34 ` [PATCH] " Michael Eager
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='CAL1P33x=wanLORS1f5tdHYYWL0Bf6_HXDRDXj3VDY6pKbCNWZA@mail.gmail.com' \
--to=gopi@sankhya.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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