From: Tom Tromey <tom@tromey.com>
To: "Jérôme Duval" <jerome.duval@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/8] gdb: Update Haiku support for 17.x
Date: Thu, 12 Mar 2026 11:58:54 -0600 [thread overview]
Message-ID: <87cy19rktd.fsf@tromey.com> (raw)
In-Reply-To: <20260312172336.15450-6-jerome.duval@gmail.com> (=?utf-8?B?IkrDqXLDtG1l?= Duval"'s message of "Thu, 12 Mar 2026 18:23:33 +0100")
>>>>> "Jérôme" == Jérôme Duval <jerome.duval@gmail.com> writes:
I chose this one to make a note on (see below), but also I wanted to
make a more general request --
In gdb we strive to have commits be bisectable. So while I think what
you did here -- having separate patches to upgrade to different baseline
gdb versions -- makes a great deal of sense when working out-of-tree,
for landing in gdb it would be better to squash these commits into the
appropriate spot in the series. Like I guess keeping the gdb/gdbserver
commits separate makes sense (at least from a gdb perspective, I didn't
really closely examine the patches).
Hope that makes sense.
Jérôme> + /*else
Jérôme> {
Jérôme> - solib_target_so_ops.relocate_section_addresses (so, sec);
Jérôme> - }
Jérôme> + solib_target_so_ops::relocate_section_addresses (so, sec);
Jérôme> + }*/
Jérôme> }
Also in gdb we generally don't land commented-out code. There is some
in the tree already (basically every rule is violated somewhere in the
tree) but we try not to add new instances.
So these should just be dropped from the patches, or resurrected if
that's more appropriate.
thanks,
Tom
next prev parent reply other threads:[~2026-03-12 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 17:23 [PATCH 0/8] Support for Haiku/x86-64 in GDB Jérôme Duval
2026-03-12 17:23 ` [PATCH 1/8] gdbserver: Initial Haiku support Jérôme Duval
2026-03-12 19:06 ` Kevin Buettner
2026-03-12 17:23 ` [PATCH 2/8] gdb: " Jérôme Duval
2026-03-12 18:31 ` Eli Zaretskii
2026-03-12 17:23 ` [PATCH 3/8] gdb: Update Haiku support for 16.x Jérôme Duval
2026-03-12 17:23 ` [PATCH 4/8] gdbserver: " Jérôme Duval
2026-03-12 17:23 ` [PATCH 5/8] gdb: Update Haiku support for 17.x Jérôme Duval
2026-03-12 17:58 ` Tom Tromey [this message]
2026-03-12 17:23 ` [PATCH 6/8] gdbserver: " Jérôme Duval
2026-03-12 17:23 ` [PATCH 7/8] gdb: Update Haiku support for 18.x Jérôme Duval
2026-03-12 17:23 ` [PATCH 8/8] gdbserver: " Jérôme Duval
2026-03-12 17:37 ` [PATCH 0/8] Support for Haiku/x86-64 in GDB Tom Tromey
[not found] ` <CAPZRpdPY4Uzwu5BinMEDcU=0SQEXU0ca31-p_X_ZOJzdGcobkQ@mail.gmail.com>
2026-03-12 21:42 ` Trung Nguyen
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=87cy19rktd.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jerome.duval@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