From: Simon Marchi <simark@simark.ca>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Yodel Eldar <yodel.eldar@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb/alpha: Add target description support
Date: Thu, 3 Jul 2025 12:02:05 -0400 [thread overview]
Message-ID: <5c5ae748-a3e3-46c4-9f41-e2843dbcd59f@simark.ca> (raw)
In-Reply-To: <alpine.DEB.2.21.2507022016100.56608@angie.orcam.me.uk>
On 2025-07-02 15:21, Maciej W. Rozycki wrote:
> On Wed, 2 Jul 2025, Simon Marchi wrote:
>
>>>> >From my non-Alpha-expert point of view, the series LGTM, so I'm tempted
>>>> to approve it. Maciej, did you have some comments on the code? Does it
>>>> look good to you?
>>>
>>> I've skimmed over now and found one minor formatting nit only, which I do
>>> hope you can address as you push this change. Otherwise if there turns
>>> out indeed anything wrong with the code later on, it can be dealt with as
>>> required. I'm not prepared right now for any further verification of this
>>> target.
>>
>> I didn't fix any formatting problem other than the one pointed out by
>> Eli. What did you find? Or else, feel free to fix it by yourself with
>> an obvious patch.
>
> Just a place asking for a new line for legibility reasons. If you've
> already pushed the change, then I can apply a follow-up update myself.
>
> Maciej
Ah ok, I missed that message. I just pushed this:
From 01d8dc11f18d774bc92b0b752e36510f86c6725c Mon Sep 17 00:00:00 2001
From: Simon Marchi <simon.marchi@polymtl.ca>
Date: Thu, 3 Jul 2025 12:00:49 -0400
Subject: [PATCH] gdb/alpha-tdep: add empty line
This was suggested in review, to separate the comment from the following
code.
Change-Id: I077ad4545ee5ef1d362dcfacf585400e26dfdb29
---
gdb/alpha-tdep.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/alpha-tdep.c b/gdb/alpha-tdep.c
index 5e8a7a02c2fa..d655c13b8293 100644
--- a/gdb/alpha-tdep.c
+++ b/gdb/alpha-tdep.c
@@ -1829,6 +1829,7 @@ INIT_GDB_FILE (alpha_tdep)
gdbarch_register (bfd_arch_alpha, alpha_gdbarch_init, NULL);
initialize_tdesc_alpha ();
+
/* Let the user set the fence post for heuristic_proc_start. */
/* We really would like to have both "0" and "unlimited" work, but
base-commit: 239f72374aab88a5b16855c01e75ed2c5b10960f
--
2.50.0
next prev parent reply other threads:[~2025-07-03 16:02 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
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 [this message]
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=5c5ae748-a3e3-46c4-9f41-e2843dbcd59f@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=yodel.eldar@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