From: Yao Qi <qiyaoltc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: time to create the GDB 8.1.x branch?
Date: Wed, 22 Nov 2017 13:07:00 -0000 [thread overview]
Message-ID: <86h8tmsbrg.fsf@gmail.com> (raw)
In-Reply-To: <20171120191510.clz2ywdyknuftzrh@adacore.com> (Joel Brobecker's message of "Mon, 20 Nov 2017 11:15:10 -0800")
Joel Brobecker <brobecker@adacore.com> writes:
> Are there any changes that would be worth waiting for before we branch
> 8.1? If not, I plan on creating the branch next Monday (Nov 27th).
Hi Joel,
Arm still has pending patch series about new ARMv8.3-A Pointer
Authentication feature support in GDB. They were posted in Aug, and
reviewed,
https://sourceware.org/ml/gdb-patches/2017-08/msg00174.html
https://sourceware.org/ml/gdb-patches/2017-08/msg00175.html
https://sourceware.org/ml/gdb-patches/2017-08/msg00171.html
https://sourceware.org/ml/gdb-patches/2017-08/msg00172.html
https://sourceware.org/ml/gdb-patches/2017-08/msg00173.html
https://sourceware.org/ml/gdb-patches/2017-08/msg00176.html
The GDB support needs the new regset provided by Linux kernel, so
these GDB patches can't go in until the kernel patches are merged.
I think kernel patches will be merged in several (5?) weeks, is it OK to
get these GDB patches into 8.1 release (mainline first and backport to
8.1 branch)? To be clear, I don't expect GDB 8.1 release should be
delayed in case that kernel patches merge won't happen in several weeks.
The reason I ask this is that I want to make sure we are OK to merge
such new feature support to release branch.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-11-22 13:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 19:15 Joel Brobecker
2017-11-21 10:50 ` Ulrich Weigand
2017-11-27 21:55 ` Joel Brobecker
2017-11-28 19:44 ` Ulrich Weigand
2017-11-28 20:32 ` Pedro Alves
2017-11-29 13:20 ` Pedro Alves
2017-11-29 21:00 ` Joel Brobecker
2017-11-29 21:49 ` Pedro Alves
2017-11-29 22:20 ` Joel Brobecker
2017-11-21 11:10 ` Yao Qi
2017-11-21 12:39 ` Pedro Alves
2017-11-27 22:20 ` Joel Brobecker
2017-11-27 22:41 ` Pedro Alves
2017-11-29 20:56 ` Joel Brobecker
2017-11-29 22:20 ` Pedro Alves
2017-11-29 22:46 ` Joel Brobecker
2017-11-22 13:07 ` Yao Qi [this message]
2017-11-27 22:06 ` Joel Brobecker
2017-11-27 22:14 ` Joel Brobecker
2017-11-28 12:38 ` Yao Qi
2017-11-29 20:58 ` Joel Brobecker
2017-11-22 18:03 ` Sergio Durigan Junior
2017-11-27 22:23 ` Joel Brobecker
2017-11-28 17:08 ` Sergio Durigan Junior
2017-11-23 15:16 ` Pedro Alves
2017-11-23 16:50 ` Joel Brobecker
2017-11-23 17:32 ` Pedro Alves
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=86h8tmsbrg.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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