From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Joel Brobecker <brobecker@adacore.com>, Tom Tromey <tom@tromey.com>
Cc: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: GDB 12 preparation and target date?
Date: Fri, 28 Jan 2022 11:03:14 +0800 [thread overview]
Message-ID: <9bdc924e-6e56-7aee-f043-0bc076e47845@loongson.cn> (raw)
In-Reply-To: <YfIXj5eJ9Nis217H@adacore.com>
On 01/27/2022 11:54 AM, Joel Brobecker via Gdb-patches wrote:
> Hi Tom,
>
> On Wed, Jan 26, 2022 at 08:07:22AM -0700, Tom Tromey wrote:
>> Joel> - GDB 12 branching 2 months from now (~Mar 20-25);
>> Joel> - GDB 12.1 release 2 weeks later, so early Apr.
>>
>> Joel> In terms of patches, I think it would be useful to start listing
>> Joel> the fixes and enhancements we'd like to include in GDB 12, and
>> Joel> keep track of them. If possible, it helps if the patches have
>> Joel> a corresponding GDB PR with the the target milestone set to 12.1.
>>
>> Joel> Let me know what you guys think, and also please let us know what
>> Joel> patches you think should be included in GDB 12, and why they are
>> Joel> important.
>>
>> I personally wouldn't mind it even a bit sooner, but this plan is also
>> fine by me.
>
> That would be fine for me as well. Let's call try to aim for early
> March? From experience, it's been tough for us to converge in that
> kind of time frame, but we can certainly try!
>
>> As for patches, I guess it would be good if we could get through the
>> backlog of unreviewed patches, at least those not from global
>> maintainers. Not that all of these could land, but at least they could
>> be not in limbo.
>
> Agreed.
>
> If people send me the URLs of the patches that are still waiting
> for review, I'm happy to keep track of their progress.
>
Hi,
Please take a look at the following patches at your convenience, thank you.
[PATCH v2 0/5] gdb: Add basic support for LoongArch
https://sourceware.org/pipermail/gdb-patches/2022-January/185318.html
[PATCH v2 1/5] gdb: LoongArch: Add initial target description support
https://sourceware.org/pipermail/gdb-patches/2022-January/185314.html
[PATCH v2 2/5] gdb: LoongArch: Add initial baremetal support
https://sourceware.org/pipermail/gdb-patches/2022-January/185316.html
[PATCH v2 3/5] gdb: LoongArch: Add initial Linux target support
https://sourceware.org/pipermail/gdb-patches/2022-January/185315.html
[PATCH v2 4/5] gdb: LoongArch: Add initial native Linux support
https://sourceware.org/pipermail/gdb-patches/2022-January/185317.html
[PATCH v2 5/5] gdb: LoongArch: Add Makefile, configure and NEWS
https://sourceware.org/pipermail/gdb-patches/2022-January/185319.html
[PATCH v3] gdb: testsuite: fix wrong expected result in
attach-pie-noexec.exp
https://sourceware.org/pipermail/gdb-patches/2022-January/184894.html
Thanks,
Tiezhu
next prev parent reply other threads:[~2022-01-28 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 11:00 Joel Brobecker
2022-01-26 15:07 ` Tom Tromey
2022-01-27 3:54 ` Joel Brobecker
2022-01-28 3:03 ` Tiezhu Yang [this message]
2022-01-28 9:40 ` Aktemur, Tankut Baris
2022-02-02 17:00 ` Andrew Burgess
2022-02-02 19:31 ` John Baldwin
2022-02-13 14:33 ` Joel Brobecker
2022-02-14 18:51 ` John Baldwin
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=9bdc924e-6e56-7aee-f043-0bc076e47845@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).